public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "su at cs dot ucdavis.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/61602] [4.10 Regression] ICE in lto1 on x86_64-linux-gnu in ipa_single_use, at ipa.c:1257 Date: Wed, 09 Jul 2014 05:40:00 -0000 [thread overview] Message-ID: <bug-61602-4-Z4ErxvS5Kk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61602-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61602 --- Comment #1 from Zhendong Su <su at cs dot ucdavis.edu> --- To help diagnose the issue, here is another test case that triggers the same ICE without using LTO. $ gcc-trunk -v Using built-in specs. COLLECT_GCC=gcc-trunk COLLECT_LTO_WRAPPER=/usr/local/gcc-trunk/libexec/gcc/x86_64-unknown-linux-gnu/4.10.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: ../gcc-trunk/configure --prefix=/usr/local/gcc-trunk --enable-languages=c,c++ --disable-werror --enable-multilib Thread model: posix gcc version 4.10.0 20140708 (experimental) [trunk revision 212357] (GCC) $ $ gcc-trunk -O1 -c small.c small.c:9:1: internal compiler error: in ipa_single_use, at ipa.c:1255 } ^ 0x81fc21 ipa_single_use ../../gcc-trunk/gcc/ipa.c:1255 0x81fc21 execute ../../gcc-trunk/gcc/ipa.c:1303 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. $ ------------------------------------------- static int a, *b = &a, **c = &b, ***d = &c; int main () { d = 0; b = 0; return 0; }
next prev parent reply other threads:[~2014-07-09 5:40 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-61602-4@http.gcc.gnu.org/bugzilla/> 2014-06-25 8:29 ` rguenth at gcc dot gnu.org 2014-07-09 5:40 ` su at cs dot ucdavis.edu [this message] 2014-07-09 8:00 ` jakub at gcc dot gnu.org 2014-08-06 0:03 ` su at cs dot ucdavis.edu 2014-11-19 13:30 ` [Bug ipa/61602] [5 " tbsaunde at gcc dot gnu.org 2014-11-19 13:51 ` rguenth at gcc dot gnu.org 2014-11-22 8:41 ` trippels at gcc dot gnu.org 2014-12-15 3:55 ` hubicka at gcc dot gnu.org 2014-12-15 4:11 ` hubicka at gcc dot gnu.org 2014-12-15 6:20 ` hubicka at gcc dot gnu.org 2014-12-15 7:08 ` hubicka 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-61602-4-Z4ErxvS5Kk@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).