public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/50602] ICE in tree_nrv, at tree-nrv.c:155 during large LTO build
Date: Sun, 09 Oct 2011 04:06:00 -0000 [thread overview]
Message-ID: <bug-50602-4-45lrTZQPQX@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 #6 from Andi Kleen <andi-gcc at firstfloor dot org> 2011-10-09 04:05:52 UTC ---
i changed the code now to save ret_val in a volatile global.
This is a bit better
(gdb) p saved_ret_val
$5 = (volatile tree) 0x2afc557b68c0
(gdb) p result
$6 = (tree_node *) 0x2afbfb754a00
Still not sure how to print them, maybe stderr is broken.
Looking at raw output I see one of them is a VAR_DECL and the other
a RESULT_DECL
(gdb) p result->decl_minimal.uid
$9 = 83837
(gdb) p saved_ret_val->decl_minimal.uid
$10 = 3599083
(gdb) p cfun->decl->decl_minimal.uid
$3 = 83835
Searching for the second uid in the dump files I see it first in
045i.whole-program:
<bb 7>:
return D.3599083;
and the first doesn't appear in any file (that means the current pass added
it?)
The third is first in 049.inline
next prev parent reply other threads:[~2011-10-09 4:06 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 [this message]
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
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-45lrTZQPQX@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).