On Sat, Mar 26, 2011 at 4:16 AM, Ramana Radhakrishnan
wrote:
> Hi Michael,
>
> Thanks for running these. I spent some time this morning looking
> through the results, they largely look ok though I don't have much
> perspective on the
> the objc/ obj-c++ failures.
>
> These failures here
>
> For v7
> Hi Michael,
>
> Thanks for running these. I spent some time this morning looking
> through the results, they largely look ok though I don't have much
> perspective on the the objc/ obj-c++ failures.
I had a quick look at the test results for 4.6.0 under Michael's
name on the mailing list.
The
On Fri, Mar 25, 2011 at 10:28:33AM -0700, Joe Buck wrote:
> On Mon, Mar 21, 2011 at 03:12:14PM -0700, Jakub Jelinek wrote:
> > A second GCC 4.6.0 release candidate is available at:
> >
> > ftp://gcc.gnu.org/pub/gcc/snapshots/4.6.0-RC-20110321/
> >
> > Please test the tarballs and report any probl
On Mon, Mar 21, 2011 at 03:12:14PM -0700, Jakub Jelinek wrote:
> A second GCC 4.6.0 release candidate is available at:
>
> ftp://gcc.gnu.org/pub/gcc/snapshots/4.6.0-RC-20110321/
>
> Please test the tarballs and report any problems to Bugzilla.
> CC me on the bugs if you believe they are regressio
Hi Michael,
Thanks for running these. I spent some time this morning looking
through the results, they largely look ok though I don't have much
perspective on the
the objc/ obj-c++ failures.
These failures here
For v7-a , A9 and Neon - these failures below:
> Running target unix
> FAIL: gfortra
On Tue, Mar 22, 2011 at 11:12 AM, Jakub Jelinek wrote:
> A second GCC 4.6.0 release candidate is available at:
>
> ftp://gcc.gnu.org/pub/gcc/snapshots/4.6.0-RC-20110321/
>
> Please test the tarballs and report any problems to Bugzilla.
> CC me on the bugs if you believe they are regressions from
>
A second GCC 4.6.0 release candidate is available at:
ftp://gcc.gnu.org/pub/gcc/snapshots/4.6.0-RC-20110321/
Please test the tarballs and report any problems to Bugzilla.
CC me on the bugs if you believe they are regressions from
previous releases severe enough to block the 4.6.0 release.
If no