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/45720] [4.6 regression] Revision 164367 miscompiled SPEC CPU 2K
Date: Fri, 22 Oct 2010 00:29:00 -0000	[thread overview]
Message-ID: <20101022002900.rdODotdCsiEMK95HP9aBAo309COIxWWh2KOspMLj4AM@z> (raw)
In-Reply-To: <bug-45720-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45720

--- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> 2010-10-22 00:28:51 UTC ---
With SPEC CPU 2006, revision 165771 gave me:

1. 64bit using-O3 -funroll-loops -ffast-math:

  Running 450.soplex ref peak lnx32e-gcc default

450.soplex: copy 0 non-zero return code (exit code=0, signal=11)

  Running 481.wrf ref peak lnx32e-gcc default

481.wrf: copy 0 non-zero return code (exit code=0, signal=11)

2. 32bit using -O3 -funroll-loops -msse2 -mfpmath=sse -ffast-math:  

  Running 481.wrf ref peak lnx32-gcc default

481.wrf: copy 0 non-zero return code (exit code=0, signal=11)


  parent reply	other threads:[~2010-10-22  0:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-45720-4@http.gcc.gnu.org/bugzilla/>
2010-09-29 19:33 ` rguenth at gcc dot gnu.org
2010-10-21 10:04 ` rguenth at gcc dot gnu.org
2010-10-21 16:28 ` hjl.tools at gmail dot com
2010-10-22  0:29 ` hjl.tools at gmail dot com [this message]
2010-10-22  4:29 ` vladimir.a.kharchenko at intel dot com
2010-10-22  9:00 ` rguenth at gcc dot gnu.org
2010-10-22 10:16 ` vladimir.a.kharchenko at intel dot com
2010-10-22 11:21 ` ubizjak at gmail dot com
2010-10-22 12:26 ` rguenth at gcc dot gnu.org
2010-10-22 13:22 ` rguenth at gcc dot gnu.org
2010-10-22 14:45 ` rguenth at gcc dot gnu.org
2010-10-23  2:09 ` hjl.tools at gmail dot com
2010-09-18 15:56 [Bug middle-end/45720] New: " hjl dot tools at gmail dot com
2010-09-18 16:29 ` [Bug middle-end/45720] " hjl dot tools at gmail dot com
2010-09-18 18:46 ` rguenth at gcc dot gnu dot 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=20101022002900.rdODotdCsiEMK95HP9aBAo309COIxWWh2KOspMLj4AM@z \
    --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: link
Be 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).