public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "matt at use dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/50490] New: ICE when compiling libglib2.0 with LTO Date: Thu, 22 Sep 2011 22:34:00 -0000 [thread overview] Message-ID: <bug-50490-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50490 Bug #: 50490 Summary: ICE when compiling libglib2.0 with LTO Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: lto AssignedTo: unassigned@gcc.gnu.org ReportedBy: matt@use.net Created attachment 25345 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25345 pre-processed source of the file that triggers the ICE with trunk revision 178863: " gcc -O2 -flto -c mem-overflow.i /home/matt/src/glib2.0-2.29.92/./glib/tests/mem-overflow.c:137:1: internal compiler error: tree code 'optimization_node' is not supported in LTO streams " changing the -O2 to -O1 eliminates the ICE. valgrind shows nothing out of the ordinary. pre-processed file mentioned in the commandline above is attached.
next reply other threads:[~2011-09-22 22:17 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-22 22:34 matt at use dot net [this message] 2011-11-19 15:21 ` [Bug lto/50490] ICE when compiling libglib2.0 with LTO, tree code 'optimization_node' is not supported in LTO streams reichelt at gcc dot gnu.org 2012-01-05 15:00 ` rguenth at gcc dot gnu.org 2012-01-05 15:44 ` rguenth at gcc dot gnu.org 2012-01-07 11:03 ` reichelt 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-50490-4@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: linkBe 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).