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/50644] ICE in set_is_used added today
Date: Thu, 20 Oct 2011 16:45:00 -0000	[thread overview]
Message-ID: <bug-50644-4-8dNXBcinW4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50644-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50644

--- Comment #13 from Andi Kleen <andi-gcc at firstfloor dot org> 2011-10-20 16:44:42 UTC ---
I only have a core file. It's really hard to catch the correct lto1
in gdb in a complex LTO build. The only sane way I found to at least
get some gdb information is to use -dH and use the corefile.
But then calling debug_tree doesn't work of course.


  parent reply	other threads:[~2011-10-20 16:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06 23:33 [Bug tree-optimization/50644] New: " andi-gcc at firstfloor dot org
2011-10-06 23:54 ` [Bug tree-optimization/50644] " andi-gcc at firstfloor dot org
2011-10-07 15:46 ` matz at gcc dot gnu.org
2011-10-07 16:31 ` jakub at gcc dot gnu.org
2011-10-07 16:35 ` matz at gcc dot gnu.org
2011-10-13 13:24 ` andi-gcc at firstfloor dot org
2011-10-13 14:05 ` matz at gcc dot gnu.org
2011-10-20  5:54 ` andi-gcc at firstfloor dot org
2011-10-20  8:16 ` matz at gcc dot gnu.org
2011-10-20 14:06 ` andi-gcc at firstfloor dot org
2011-10-20 16:17 ` matz at gcc dot gnu.org
2011-10-20 16:31 ` andi-gcc at firstfloor dot org
2011-10-20 16:40 ` jakub at gcc dot gnu.org
2011-10-20 16:45 ` andi-gcc at firstfloor dot org [this message]
2011-10-29 11:32 ` andi-gcc at firstfloor dot org
2011-10-29 12:59 ` markus at trippelsdorf dot de
2011-10-29 13:08 ` markus at trippelsdorf dot de
2011-10-31 13:17 ` matz at gcc dot gnu.org
2011-10-31 13:38 ` matz at gcc dot gnu.org
2011-10-31 13:43 ` matz at gcc dot gnu.org
2011-11-17 16:09 ` matz at gcc dot gnu.org
2011-11-17 16:35 ` matz at gcc dot gnu.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-50644-4-8dNXBcinW4@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).