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/48367] New: [4.7 Regression] 200.sixtrack/301.apsi in SPEC CPU 2000 are miscompiled Date: Wed, 30 Mar 2011 14:55:00 -0000 [thread overview] Message-ID: <bug-48367-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48367 Summary: [4.7 Regression] 200.sixtrack/301.apsi in SPEC CPU 2000 are miscompiled 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/ia32, revision 171716 gave Running 200.sixtrack ref peak lnx32-gcc default *** Miscompare of inp.out, see /export/gnu/import/svn/gcc-test-spec/spec/2000/i6 86/spec/benchspec/CFP2000/200.sixtrack/run/00000004/inp.out.mis Running 301.apsi ref peak lnx32-gcc default *** Miscompare of APO11, see /export/gnu/import/svn/gcc-test-spec/spec/2000/i686 /spec/benchspec/CFP2000/301.apsi/run/00000004/APO11.mis *** Miscompare of APO6, see /export/gnu/import/svn/gcc-test-spec/spec/2000/i686/ spec/benchspec/CFP2000/301.apsi/run/00000004/APO6.mis *** Miscompare of APO8, see /export/gnu/import/svn/gcc-test-spec/spec/2000/i686/ spec/benchspec/CFP2000/301.apsi/run/00000004/APO8.mis *** Miscompare of APV, see /export/gnu/import/svn/gcc-test-spec/spec/2000/i686/s pec/benchspec/CFP2000/301.apsi/run/00000004/APV.mis Revision 171623 is OK.
next reply other threads:[~2011-03-30 14:51 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-30 14:55 hjl.tools at gmail dot com [this message] 2011-03-30 15:01 ` [Bug middle-end/48367] " rguenth at gcc dot gnu.org 2011-03-30 16:53 ` hjl.tools at gmail dot com 2011-03-30 17:00 ` hjl.tools at gmail dot com 2011-03-30 17:02 ` hjl.tools at gmail dot com 2011-03-31 0:02 ` vmakarov at redhat dot com 2011-03-31 3:18 ` vmakarov at gcc dot gnu.org 2011-03-31 3:27 ` vmakarov at redhat dot com 2011-04-12 16:15 ` 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-48367-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).