From: Jakub Jelinek <jakub@redhat.com>
To: Joe Buck <Joe.Buck@synopsys.COM>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Second GCC 4.6.0 release candidate is now available
Date: Fri, 25 Mar 2011 17:50:00 -0000 [thread overview]
Message-ID: <20110325173935.GD18914@tyan-ft48-01.lab.bos.redhat.com> (raw)
In-Reply-To: <20110325172833.GR5293@synopsys.com>
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 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.
>
> See http://gcc.gnu.org/ml/gcc-testresults/2011-03/msg02463.html .
>
> There's an ICE for gcc.c-torture/compile/limits-exprparen.c
> which might be an issue. I think that the others may be due
limits-exprparen.c is http://gcc.gnu.org/PR31827, certainly not a recent
regression that should block 4.6.0 release and probably nothing
you will encounter in real-world testcases, furthermore
for many hosts there is a workaround, just increase ulimit -s limit.
Jakub
prev parent reply other threads:[~2011-03-25 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 17:22 Jakub Jelinek
2011-03-21 22:13 ` Second " Jakub Jelinek
2011-03-24 22:58 ` Michael Hope
2011-03-25 15:47 ` Ramana Radhakrishnan
2011-03-25 18:03 ` Nicola Pero
2011-04-04 21:21 ` Michael Hope
2011-03-25 17:37 ` Joe Buck
2011-03-25 17:50 ` Jakub Jelinek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110325173935.GD18914@tyan-ft48-01.lab.bos.redhat.com \
--to=jakub@redhat.com \
--cc=Joe.Buck@synopsys.COM \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).