public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "PHHargrove at lbl dot gov" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/55433] New: [4.8 Regression] ICE on excessive reloads Date: Wed, 21 Nov 2012 22:41:00 -0000 [thread overview] Message-ID: <bug-55433-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55433 Bug #: 55433 Summary: [4.8 Regression] ICE on excessive reloads Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: PHHargrove@lbl.gov CC: gary@intrepid.com, nenad@intrepid.com The 9-line stand-alone test case at the end of this report fails as show below on MacOS (at least versions 10.6 and 10.8) on x86-64 machines when targeting the ILP32 ABI. It notably does NOT fail on Linux/x86-64. This was seen in SVN r193679 (on MacOSX 10.6) and r193709 (on MacOSX 10.8). --cut-- $ gcc -m32 -O1 -fpreprocessed -c testcase.c testcase.c: In function 'test': testcase.c:10:1: internal compiler error: Max. number of generated reload insns per insn is achieved (90) } ^ testcase.c:9:1: internal compiler error: Abort trap gcc: internal compiler error: Abort trap (program cc1) Abort trap --cut-- Note that while the error message is the same as bug 55247, I have confirmed that the test case attached to that bug report has NOT regressed. Therefore, I believe this is a different bug (though possibly related). Some additional data: + -m32 is required (no bug seen w/ -m64) + Linux host is fine (w/ -m32 and -m64) + -O1 is sufficient, but -O2 and -O3 fail in the same manner + removing "unsigned" from the typedef eliminates the problem + adding -mno-sse to the command line eliminates the problem The testcase: typedef unsigned long long tick_t; // NOTE: no bug if "unsigned" is removed extern int foo(void); extern tick_t tick(void); double test(void) { struct { tick_t ticks; } st; st.ticks = tick(); foo(); // NOTE: no bug if this call is removed return (double)st.ticks; }
next reply other threads:[~2012-11-21 22:41 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-21 22:41 PHHargrove at lbl dot gov [this message] 2012-11-21 22:48 ` [Bug target/55433] " PHHargrove at lbl dot gov 2012-11-25 15:55 ` rguenth at gcc dot gnu.org 2012-12-07 10:20 ` [Bug target/55433] [4.8 Regression][LRA] " rguenth at gcc dot gnu.org 2013-01-15 9:16 ` PHHargrove at lbl dot gov 2013-01-16 18:44 ` vmakarov at gcc dot gnu.org 2013-01-18 18:15 ` vmakarov at gcc dot gnu.org 2013-01-18 20:31 ` jakub at gcc dot gnu.org 2013-01-20 19:10 ` vmakarov 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-55433-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).