On Tue, Jun 21, 2011 at 1:01 AM, Jakub Jelinek wrote:
> The first release candidate for GCC 4.6.1 is available from
>
> ftp://gcc.gnu.org/pub/gcc/snapshots/4.6.1-RC-20110620
>
> and shortly its mirrors. It has been generated from SVN revision 175201.
>
> I have so far bootstrapped and tested the
On Wed, Jun 22, 2011 at 11:21:16PM +0200, Paweł Sikora wrote:
> On Monday, June 20, 2011 03:01:47 PM Jakub Jelinek wrote:
> > The first release candidate for GCC 4.6.1 is available from
> >
> > ftp://gcc.gnu.org/pub/gcc/snapshots/4.6.1-RC-20110620
> >
> > and shortly its mirrors. It has been g
On Monday, June 20, 2011 03:01:47 PM Jakub Jelinek wrote:
> The first release candidate for GCC 4.6.1 is available from
>
> ftp://gcc.gnu.org/pub/gcc/snapshots/4.6.1-RC-20110620
>
> and shortly its mirrors. It has been generated from SVN revision 175201.
>
> I have so far bootstrapped and tes
> I guess it depends on how risky the patch is, while reorg.c affects only a
> few targets, they still include some primary targets. If it is not a
> regression from 4.6.0 and the fix isn't very obviously safe, it would
> probably be better to postpone it for 4.6.2 (though, I think CPU cycles
> wo
On Tue, Jun 21, 2011 at 10:47:54AM +0200, Eric Botcazou wrote:
> > I have so far bootstrapped and tested the release candidate on
> > x86_64-linux and i686-linux. Please test it and report any issues to
> > bugzilla.
>
> They aren't really regressions from 4.6.0 but on SPARC/Solaris we have:
>
>
> I have so far bootstrapped and tested the release candidate on
> x86_64-linux and i686-linux. Please test it and report any issues to
> bugzilla.
They aren't really regressions from 4.6.0 but on SPARC/Solaris we have:
FAIL: gcc.dg/vect/pr48377.c execution test (you know what I mean)
FAIL: g++
