public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/57597] New: ICE: in get_section, at varasm.c:312: Segmentation fault Date: Wed, 12 Jun 2013 14:02:00 -0000 [thread overview] Message-ID: <bug-57597-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57597 Bug ID: 57597 Summary: ICE: in get_section, at varasm.c:312: Segmentation fault Product: gcc Version: 4.8.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: gjl at gcc dot gnu.org Host: i386-mingw32 Target: avr Build: i686-linux-gnu Created attachment 30299 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30299&action=edit foo.c: C test case Compile the test case with avr-gcc -mmcu=atmega168 -S foo.c -fmerge-all-constants -O foo.c:12:1: internal compiler error: in get_section, at varasm.c:312 } ^ foo.c:12:1: internal compiler error: Segmentation fault This might be related to PR50739 == configure == Configured with: ../../gcc.gnu.org/trunk/configure --target=avr --prefix=/local/gnu/install/gcc-4.8-mingw32 --host=i386-mingw32 --build=i686-linux-gnu --enable-languages=c,c++ --disable-nls --disable-shared --with-dwarf2 Thread model: single gcc version 4.8.0 20130306 (experimental) (GCC)
next reply other threads:[~2013-06-12 14:02 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-12 14:02 gjl at gcc dot gnu.org [this message] 2013-06-12 14:03 ` [Bug other/57597] ICE: in get_section, at varasm.c:312: Segmentation fault with -fmerge-all-constants gjl at gcc dot gnu.org 2015-03-30 4:05 ` [Bug target/57597] " gjl at gcc dot gnu.org 2024-03-15 22:16 ` pinskia 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-57597-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).