public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andi at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/50602] ICE in tree_nrv, at tree-nrv.c:155 during large LTO build
Date: Mon, 07 May 2012 13:09:00 -0000 [thread overview]
Message-ID: <bug-50602-4-fDDJHd58fp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50602-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50602
--- Comment #24 from andi at firstfloor dot org 2012-05-07 13:08:08 UTC ---
On Mon, May 07, 2012 at 08:54:10AM +0000, rguenther at suse dot de wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50602
>
> --- Comment #23 from rguenther at suse dot de <rguenther at suse dot de> 2012-05-07 08:54:10 UTC ---
> On Sat, 5 May 2012, hubicka at gcc dot gnu.org wrote:
>
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50602
> >
> > Jan Hubicka <hubicka at gcc dot gnu.org> changed:
> >
> > What |Removed |Added
> > ----------------------------------------------------------------------------
> > CC| |hubicka at gcc dot gnu.org
> >
> > --- Comment #22 from Jan Hubicka <hubicka at gcc dot gnu.org> 2012-05-05 10:02:15 UTC ---
> > great, backporting to 4.7 should be easy, right?
>
> I'm not sure we should backport option handling changes. In general
> we still expect consistent options at compile and link time (that did
> not change in 4.7 - what changed was the implementation).
I worked around it in my kernel build, so it's not critial.
But there are other problems back now :-(
-Andi
prev parent reply other threads:[~2012-05-07 13:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 16:40 [Bug tree-optimization/50602] New: " andi-gcc at firstfloor dot org
2011-10-03 16:41 ` [Bug tree-optimization/50602] " andi-gcc at firstfloor dot org
2011-10-04 11:04 ` rguenth at gcc dot gnu.org
2011-10-04 13:22 ` andi-gcc at firstfloor dot org
2011-10-04 14:20 ` rguenth at gcc dot gnu.org
2011-10-09 2:31 ` andi-gcc at firstfloor dot org
2011-10-09 4:06 ` andi-gcc at firstfloor dot org
2011-10-29 12:12 ` andi-gcc at firstfloor dot org
2011-10-30 14:23 ` steven at gcc dot gnu.org
2011-10-30 15:53 ` andi-gcc at firstfloor dot org
2011-11-23 0:44 ` andi-gcc at firstfloor dot org
2012-01-07 22:18 ` pinskia at gcc dot gnu.org
2012-01-08 1:38 ` andi-gcc at firstfloor dot org
2012-05-02 14:24 ` andi-gcc at firstfloor dot org
2012-05-02 14:51 ` markus at trippelsdorf dot de
2012-05-02 15:19 ` markus at trippelsdorf dot de
2012-05-03 14:52 ` [Bug lto/50602] " rguenth at gcc dot gnu.org
2012-05-03 14:58 ` andi-gcc at firstfloor dot org
2012-05-04 8:18 ` rguenther at suse dot de
2012-05-04 11:01 ` rguenth at gcc dot gnu.org
2012-05-04 11:47 ` rguenth at gcc dot gnu.org
2012-05-04 11:49 ` rguenth at gcc dot gnu.org
2012-05-05 10:06 ` hubicka at gcc dot gnu.org
2012-05-07 9:01 ` rguenther at suse dot de
2012-05-07 13:09 ` andi at firstfloor dot org [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=bug-50602-4-fDDJHd58fp@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).