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 middle-end/50528] New: [4.7 Regression] SPEC CPU 2006 failed to build with LTO Date: Mon, 26 Sep 2011 17:07:00 -0000 [thread overview] Message-ID: <bug-50528-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50528 Bug #: 50528 Summary: [4.7 Regression] SPEC CPU 2006 failed to build with LTO Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned@gcc.gnu.org ReportedBy: hjl.tools@gmail.com On Linux/x86-64, revision 179164 failed to build 416.gamess, 447.dealII and 481.wrf with LTO. Failure is gfortran -O2 -ffast-math -fwhole-program -flto=jobserver -fuse-linker-plugin -DSPEC_CPU_LP64 ... lto1: internal compiler error: in account_size_time, at ipa-inline-analysis.c:601 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. lto-wrapper: gfortran returned 1 exit status /usr/local/bin/ld: lto-wrapper failed collect2: error: ld returned 1 exit status Revision 179104 is OK.
next reply other threads:[~2011-09-26 16:29 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-26 17:07 hjl.tools at gmail dot com [this message] 2011-09-26 18:11 ` [Bug middle-end/50528] " hjl.tools at gmail dot com 2011-09-26 18:29 ` hubicka at gcc dot gnu.org 2011-09-27 9:21 ` rguenth at gcc dot gnu.org 2011-10-10 14:21 ` 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-50528-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).