public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ishiura-compiler at ml dot kwansei.ac.jp" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/61010] New: ICE in gcc.c Date: Wed, 30 Apr 2014 02:02:00 -0000 [thread overview] Message-ID: <bug-61010-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61010 Bug ID: 61010 Summary: ICE in gcc.c Product: gcc Version: 4.10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: ishiura-compiler at ml dot kwansei.ac.jp GCC 4.8 - 4.10 for i686 and x86_64 ICE the following code. /* $ x86_64-unknown-linux-gnu-gcc-4.10.0 test.c x86_64-unknown-linux-gnu-gcc-4.10.0: internal compiler error: Segmentation fault (program cc1) 0x40ce59 execute /home/hassy/gcc-master/gcc/gcc.c:2848 0x40d0c9 do_spec_1 /home/hassy/gcc-master/gcc/gcc.c:4652 0x40fd76 process_brace_body /home/hassy/gcc-master/gcc/gcc.c:5935 0x40fd76 handle_braces /home/hassy/gcc-master/gcc/gcc.c:5849 0x40deb7 do_spec_1 /home/hassy/gcc-master/gcc/gcc.c:5306 0x40fd76 process_brace_body /home/hassy/gcc-master/gcc/gcc.c:5935 0x40fd76 handle_braces /home/hassy/gcc-master/gcc/gcc.c:5849 0x40deb7 do_spec_1 /home/hassy/gcc-master/gcc/gcc.c:5306 0x40ddbe do_spec_1 /home/hassy/gcc-master/gcc/gcc.c:5421 0x40fd76 process_brace_body /home/hassy/gcc-master/gcc/gcc.c:5935 0x40fd76 handle_braces /home/hassy/gcc-master/gcc/gcc.c:5849 0x40deb7 do_spec_1 /home/hassy/gcc-master/gcc/gcc.c:5306 0x40fd76 process_brace_body /home/hassy/gcc-master/gcc/gcc.c:5935 0x40fd76 handle_braces /home/hassy/gcc-master/gcc/gcc.c:5849 0x40deb7 do_spec_1 /home/hassy/gcc-master/gcc/gcc.c:5306 0x40fd76 process_brace_body /home/hassy/gcc-master/gcc/gcc.c:5935 0x40fd76 handle_braces /home/hassy/gcc-master/gcc/gcc.c:5849 0x40deb7 do_spec_1 /home/hassy/gcc-master/gcc/gcc.c:5306 0x40fd76 process_brace_body /home/hassy/gcc-master/gcc/gcc.c:5935 0x40fd76 handle_braces /home/hassy/gcc-master/gcc/gcc.c:5849 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. $ x86_64-unknown-linux-gnu-gcc-4.10.0 -v Using built-in specs. COLLECT_GCC=x86_64-unknown-linux-gnu-gcc-4.10.0 COLLECT_LTO_WRAPPER=/usr/local/x86_64-tools/gcc-4.10.0/libexec/gcc/x86_64-unknown-linux-gnu/4.10.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: /home/hassy/gcc-master/configure --prefix=/usr/local/x86_64-tools/gcc-4.10.0/ --with-gmp=/usr/local/gmp-5.1.1/ --with-mpfr=/usr/local/mpfr-3.1.2/ --with-mpc=/usr/local/mpc-1.0.2/ --disable-multilib --disable-nls --enable-languages=c Thread model: posix gcc version 4.10.0 20140429 (experimental) (GCC) */ int main (void) { int a = 0; unsigned b = (a * 64 & 192) | 63U; return 0; }
next reply other threads:[~2014-04-30 2:02 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-30 2:02 ishiura-compiler at ml dot kwansei.ac.jp [this message] 2014-04-30 2:28 ` [Bug middle-end/61010] " pinskia at gcc dot gnu.org 2014-04-30 6:00 ` mpolacek at gcc dot gnu.org 2014-04-30 8:21 ` ktkachov at gcc dot gnu.org 2014-04-30 9:06 ` ktkachov at gcc dot gnu.org 2014-04-30 9:29 ` [Bug middle-end/61010] [4.8/4.9/4.10 Regression] Infinite recursion in fold rguenth at gcc dot gnu.org 2014-04-30 10:13 ` rguenth at gcc dot gnu.org 2014-04-30 10:18 ` rguenth at gcc dot gnu.org 2014-04-30 10:43 ` rguenth at gcc dot gnu.org 2014-04-30 10:43 ` rguenth at gcc dot gnu.org 2014-05-05 9:24 ` [Bug middle-end/61010] [4.8/4.9 " rguenth at gcc dot gnu.org 2014-05-05 9:24 ` rguenth at gcc dot gnu.org 2014-05-22 9:01 ` rguenth at gcc dot gnu.org 2014-05-28 12:47 ` [Bug middle-end/61010] [4.8 " rguenth at gcc dot gnu.org 2014-09-09 13:18 ` rguenth at gcc dot gnu.org 2014-09-09 13:18 ` rguenth 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-61010-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).