public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adam at os dot inf.tu-dresden.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/64068] [5 Regression] ICE: in remove_unreachable_nodes, at ipa.c:546
Date: Sat, 20 Dec 2014 10:04:00 -0000	[thread overview]
Message-ID: <bug-64068-4-MQZYMeguzj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64068-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64068

Adam Lackorzynski <adam at os dot inf.tu-dresden.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adam at os dot inf.tu-dresden.de

--- Comment #4 from Adam Lackorzynski <adam at os dot inf.tu-dresden.de> ---
Created attachment 34304
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34304&action=edit
Another test-case

This is another test-case that triggers this ICE.

$ g++ -c  -std=c++0x -m32     -O2   t.i                           
t.i:105:1: internal compiler error: in remove_unreachable_nodes, at ipa.c:574
 }
 ^
0xb2a991 symbol_table::remove_unreachable_nodes(_IO_FILE*)
        ../../gcc/gcc/ipa.c:574
0x12bc193 ipa_inline
        ../../gcc/gcc/ipa-inline.c:2196
0x12bc193 execute
        ../../gcc/gcc/ipa-inline.c:2562
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
zsh: exit 1     /usr/local/gcc/host-x86_64/head/bin/g++ -c -std=c++0x -m32 -O2 

$ g++ --version
g++ (GCC) 5.0.0 20141220 (experimental)

Adding -fno-ipa-icf also makes it go away.


  parent reply	other threads:[~2014-12-20 10:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25  9:50 [Bug ipa/64068] New: " trippels at gcc dot gnu.org
2014-11-25  9:52 ` [Bug ipa/64068] " rguenth at gcc dot gnu.org
2014-11-25 14:01 ` marxin at gcc dot gnu.org
2014-11-30 20:43 ` dimhen at gmail dot com
2014-12-02 17:39 ` burnus at gcc dot gnu.org
2014-12-20 10:04 ` adam at os dot inf.tu-dresden.de [this message]
2015-01-15  4:24 ` hubicka at gcc dot gnu.org
2015-01-15  4:27 ` hubicka at gcc dot gnu.org
2015-01-15 17:12 ` marxin at gcc dot gnu.org
2015-01-15 17:15 ` marxin at gcc dot gnu.org
2015-01-15 17:30 ` marxin at gcc dot gnu.org
2015-02-04 23:37 ` doko at gcc dot gnu.org
2015-02-05  0:28 ` wmi at gcc dot gnu.org
2015-02-19  0:44 ` ctice 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-64068-4-MQZYMeguzj@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).