public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* GCC 4.6.1 Release Candidate available from gcc.gnu.org
@ 2011-06-20 13:02 Jakub Jelinek
  2011-06-21  8:48 ` Eric Botcazou
                   ` (2 more replies)
  0 siblings, 3 replies; 7+ messages in thread
From: Jakub Jelinek @ 2011-06-20 13:02 UTC (permalink / raw)
  To: gcc

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 release candidate on
x86_64-linux and i686-linux.  Please test it and report any issues to
bugzilla.

If all goes well, I'd like to release 4.6.1 early next week.

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GCC 4.6.1 Release Candidate available from gcc.gnu.org
  2011-06-20 13:02 GCC 4.6.1 Release Candidate available from gcc.gnu.org Jakub Jelinek
@ 2011-06-21  8:48 ` Eric Botcazou
  2011-06-21  9:00   ` Jakub Jelinek
  2011-06-22 21:21 ` Paweł Sikora
  2011-06-22 22:49 ` Michael Hope
  2 siblings, 1 reply; 7+ messages in thread
From: Eric Botcazou @ 2011-06-21  8:48 UTC (permalink / raw)
  To: Jakub Jelinek; +Cc: gcc

> 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++.dg/cpp0x/lambda/lambda-eh2.C execution test (PR c++/49260)

and on SPARC64 we have an ACATS failure:

FAIL:   c94007a


The ACATS failure is a reorg.c bug, for which I have a straightforward fix, but 
I think I should first ask if you're interested in it for 4.6.1 before wasting 
CPU cycles. ;-)

-- 
Eric Botcazou

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GCC 4.6.1 Release Candidate available from gcc.gnu.org
  2011-06-21  8:48 ` Eric Botcazou
@ 2011-06-21  9:00   ` Jakub Jelinek
  2011-06-21  9:18     ` Eric Botcazou
  0 siblings, 1 reply; 7+ messages in thread
From: Jakub Jelinek @ 2011-06-21  9:00 UTC (permalink / raw)
  To: Eric Botcazou; +Cc: gcc

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:
> 
> FAIL: gcc.dg/vect/pr48377.c execution test (you know what I mean)

For this a patch is awaiting review, but it is a testsuite only issue,
so not a blocker.

> FAIL: g++.dg/cpp0x/lambda/lambda-eh2.C execution test (PR c++/49260)
> 
> and on SPARC64 we have an ACATS failure:
> 
> FAIL:   c94007a
> 
> 
> The ACATS failure is a reorg.c bug, for which I have a straightforward fix, but 
> I think I should first ask if you're interested in it for 4.6.1 before wasting 
> CPU cycles. ;-)

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 wouldn't be
wasted by preparing a fix for 4.6.2).

	Jakub

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GCC 4.6.1 Release Candidate available from gcc.gnu.org
  2011-06-21  9:00   ` Jakub Jelinek
@ 2011-06-21  9:18     ` Eric Botcazou
  0 siblings, 0 replies; 7+ messages in thread
From: Eric Botcazou @ 2011-06-21  9:18 UTC (permalink / raw)
  To: Jakub Jelinek; +Cc: gcc

> 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
> wouldn't be wasted by preparing a fix for 4.6.2).

I think it is as obviously safe as a reorg.c patch can be so I'm going to test 
it (on the branch) and post it afterward, but it will be your call of course.

-- 
Eric Botcazou

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GCC 4.6.1 Release Candidate available from gcc.gnu.org
  2011-06-20 13:02 GCC 4.6.1 Release Candidate available from gcc.gnu.org Jakub Jelinek
  2011-06-21  8:48 ` Eric Botcazou
@ 2011-06-22 21:21 ` Paweł Sikora
  2011-06-22 22:19   ` Jakub Jelinek
  2011-06-22 22:49 ` Michael Hope
  2 siblings, 1 reply; 7+ messages in thread
From: Paweł Sikora @ 2011-06-22 21:21 UTC (permalink / raw)
  To: jakub; +Cc: gcc, ktietz70

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 tested the release candidate on
> x86_64-linux and i686-linux.  Please test it and report any issues to
> bugzilla.

PR49407     - mingw / impossible .dll debug.
PR47308#c17 - mingw / problems with mixing dwarf-2/dwarf-4 objects.

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GCC 4.6.1 Release Candidate available from gcc.gnu.org
  2011-06-22 21:21 ` Paweł Sikora
@ 2011-06-22 22:19   ` Jakub Jelinek
  0 siblings, 0 replies; 7+ messages in thread
From: Jakub Jelinek @ 2011-06-22 22:19 UTC (permalink / raw)
  To: Paweł Sikora; +Cc: gcc, ktietz70

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 generated from SVN revision 175201.
> > 
> > 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.
> 
> PR49407     - mingw / impossible .dll debug.
> PR47308#c17 - mingw / problems with mixing dwarf-2/dwarf-4 objects.

Are these regressions from 4.6.0 release?  If not, they don't look like
4.6.1 release blockers.

	Jakub

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GCC 4.6.1 Release Candidate available from gcc.gnu.org
  2011-06-20 13:02 GCC 4.6.1 Release Candidate available from gcc.gnu.org Jakub Jelinek
  2011-06-21  8:48 ` Eric Botcazou
  2011-06-22 21:21 ` Paweł Sikora
@ 2011-06-22 22:49 ` Michael Hope
  2 siblings, 0 replies; 7+ messages in thread
From: Michael Hope @ 2011-06-22 22:49 UTC (permalink / raw)
  To: Jakub Jelinek; +Cc: gcc

On Tue, Jun 21, 2011 at 1:01 AM, Jakub Jelinek <jakub@redhat.com> 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 release candidate on
> x86_64-linux and i686-linux.  Please test it and report any issues to
> bugzilla.

It bootstraps C, C++ and Fortran in a ARM Cortex-A9 and ARMv5TE
configuration.  The test results are here:
 http://gcc.gnu.org/ml/gcc-testresults/2011-06/msg02632.html
 http://gcc.gnu.org/ml/gcc-testresults/2011-06/msg02633.html

with more detail here:
 http://builds.linaro.org/toolchain/gcc-4.6.1-RC-20110620/logs/

Ramana or Richard, could you have a read over the results please?

-- Michael

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2011-06-22 22:49 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-06-20 13:02 GCC 4.6.1 Release Candidate available from gcc.gnu.org Jakub Jelinek
2011-06-21  8:48 ` Eric Botcazou
2011-06-21  9:00   ` Jakub Jelinek
2011-06-21  9:18     ` Eric Botcazou
2011-06-22 21:21 ` Paweł Sikora
2011-06-22 22:19   ` Jakub Jelinek
2011-06-22 22:49 ` Michael Hope

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).