public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vincenzo.innocente at cern dot ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/53450] New: [4.8 Regression] ICE in compiling libiberty/cp-demangle.c with -O2 Date: Tue, 22 May 2012 12:34:00 -0000 [thread overview] Message-ID: <bug-53450-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53450 Bug #: 53450 Summary: [4.8 Regression] ICE in compiling libiberty/cp-demangle.c with -O2 Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned@gcc.gnu.org ReportedBy: vincenzo.innocente@cern.ch compile: /home/data/newsoft/gcc-build/./gcc/xgcc -B/home/data/newsoft/gcc-build/./gcc/ -B/afs/cern.ch/user/i/innocent/w2/x86_64-unknown-linux-gnu/bin/ -B/afs/cern.ch/user/i/innocent/w2/x86_64-unknown-linux-gnu/lib/ -isystem /afs/cern.ch/user/i/innocent/w2/x86_64-unknown-linux-gnu/include -isystem /afs/cern.ch/user/i/innocent/w2/x86_64-unknown-linux-gnu/sys-include -DHAVE_CONFIG_H -I.. -I/home/data/newsoft/gcc-trunk/libstdc++-v3/../libiberty -I/home/data/newsoft/gcc-trunk/libstdc++-v3/../include -I/home/data/newsoft/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/include/x86_64-unknown-linux-gnu -I/home/data/newsoft/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/include -I/home/data/newsoft/gcc-trunk/libstdc++-v3/libsupc++ -g -O2 -ftree-vectorize -fPIC -DIN_GLIBCPP_V3 -Wno-error -c cp-demangle.c -fPIC -DPIC -o cp-demangle.o In file included from /usr/include/string.h:637:0, from cp-demangle.c:112: cp-demangle.c: In function 'd_print_comp.part.9': cp-demangle.c:3933:16: internal compiler error: in int_mode_for_mode, at stor-layout.c:424 && strncmp (dcl->u.s_name.s, "JArray", 6) == 0) ^ cd /home/data/newsoft/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/libsupc++ [innocent@vinavx0 libsupc++]$ /home/data/newsoft/gcc-build/./gcc/xgcc -B/home/data/newsoft/gcc-build/./gcc/ -B/afs/cern.ch/user/i/innocent/w2/x86_64-unknown-linux-gnu/bin/ -B/afs/cern.ch/user/i/innocent/w2/x86_64-unknown-linux-gnu/lib/ -isystem /afs/cern.ch/user/i/innocent/w2/x86_64-unknown-linux-gnu/include -isystem /afs/cern.ch/user/i/innocent/w2/x86_64-unknown-linux-gnu/sys-include -DHAVE_CONFIG_H -I.. -I/home/data/newsoft/gcc-trunk/libstdc++-v3/../libiberty -I/home/data/newsoft/gcc-trunk/libstdc++-v3/../include -I/home/data/newsoft/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/include/x86_64-unknown-linux-gnu -I/home/data/newsoft/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/include -I/home/data/newsoft/gcc-trunk/libstdc++-v3/ -g -ftree-vectorize -fPIC -DIN_GLIBCPP_V3 -Wno-error -c cp-demangle.c -fPIC -DPIC -o cp-demangle.o succeds…
next reply other threads:[~2012-05-22 12:33 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-22 12:34 vincenzo.innocente at cern dot ch [this message] 2012-05-22 12:53 ` [Bug middle-end/53450] [4.8 Regression] ICE in compiling libiberty/cp-demangle.c with -O2 in int_mode_for_mode, at stor-layout.c:424 rguenth at gcc dot gnu.org 2012-05-22 12:54 ` markus at trippelsdorf dot de 2012-05-22 13:14 ` vincenzo.innocente at cern dot ch
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-53450-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).