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/46506] New: LTO miscompiled 465.tonto in SPEC CPU 2006 Date: Tue, 16 Nov 2010 17:48:00 -0000 [thread overview] Message-ID: <bug-46506-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46506 Summary: LTO miscompiled 465.tonto in SPEC CPU 2006 Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto AssignedTo: unassigned@gcc.gnu.org ReportedBy: hjl.tools@gmail.com On Linux/x86-64, revision 166795 with -O3 -funroll-loops -ffast-math -fwhole-program -flto=jobserver -ffixed-form gave Running 465.tonto test peak lto default *** Miscompare of stdout; for details see /export/gnu/import/svn/gcc-test-spec/spec/2006/x86_64/spec/benchspec/CPU2006 /465.tonto/run/run_peak_test_lto.0000/stdout.mis
next reply other threads:[~2010-11-16 17:44 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-16 17:48 hjl.tools at gmail dot com [this message] 2010-11-17 11:52 ` [Bug lto/46506] " rguenth at gcc dot gnu.org 2010-11-17 12:08 ` rguenth at gcc dot gnu.org 2010-11-17 13:36 ` hjl.tools at gmail dot com 2010-11-17 14:06 ` rguenth at gcc dot gnu.org 2010-11-18 1:57 ` hjl.tools at gmail dot com 2010-11-20 20:07 ` [Bug middle-end/46506] GCC " hjl.tools at gmail dot com 2010-11-20 20:21 ` hjl.tools at gmail dot com 2010-12-08 0:51 ` changpeng.fang at amd dot com 2010-12-08 0:54 ` changpeng.fang at amd dot com 2010-12-08 1:09 ` hjl.tools at gmail dot com 2010-12-09 4:06 ` hjl.tools at gmail dot com 2010-12-09 4:07 ` hjl.tools at gmail dot com
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-46506-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).