public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/46629] [4.6 Regression] Failed to build 200.sixtrack in SPEC CPU 2000 Date: Wed, 24 Nov 2010 05:03:00 -0000 [thread overview] Message-ID: <bug-46629-4-yZLIlNNsBO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46629-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46629 --- Comment #6 from H.J. Lu <hjl.tools at gmail dot com> 2010-11-24 01:09:20 UTC --- Created attachment 22504 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22504 A testcase [hjl@gnu-35 delta-fortran]$ /export/gnu/import/svn/gcc-test-spec/usr/bin/gcc -S -O3 -ffast-math -funroll-loops -msse2 -mfpmath=sse -m32 -ffast-math -fwhole-program -flto=jobserver -fuse-linker-plugin testcase-min.f testcase-min.f: In function ‘daexx_.part.0’: testcase-min.f:1:0: internal compiler error: in maybe_cleanup_end_of_block, at cfgexpand.c:1700 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. [hjl@gnu-35 delta-fortran]$
next prev parent reply other threads:[~2010-11-24 1:09 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-23 21:29 [Bug lto/46629] New: " hjl.tools at gmail dot com 2010-11-23 22:00 ` [Bug lto/46629] " hjl.tools at gmail dot com 2010-11-23 22:07 ` hjl.tools at gmail dot com 2010-11-23 23:46 ` jakub at gcc dot gnu.org 2010-11-23 23:48 ` hjl.tools at gmail dot com 2010-11-24 0:10 ` jakub at gcc dot gnu.org 2010-11-24 4:59 ` hjl.tools at gmail dot com 2010-11-24 5:03 ` hjl.tools at gmail dot com [this message] 2010-11-24 9:56 ` [Bug middle-end/46629] " jakub at gcc dot gnu.org 2010-11-24 10:40 ` jakub at gcc dot gnu.org 2010-11-24 12:02 ` jakub at gcc dot gnu.org 2010-12-07 15:23 ` jakub 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-46629-4-yZLIlNNsBO@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).