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 ipa/65028] New: [5 Regression] 450.soplex in SPEC CPU 2006 is miscompiled
Date: Wed, 11 Feb 2015 20:23:00 -0000	[thread overview]
Message-ID: <bug-65028-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65028

            Bug ID: 65028
           Summary: [5 Regression] 450.soplex in SPEC CPU 2006 is
                    miscompiled
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ipa
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hjl.tools at gmail dot com
                CC: hubicka at ucw dot cz

On Linux/x86-64, r220521 miscompiled 450.soplex in SPEC CPU 2006:

g++  -O3 -funroll-loops -ffast-math -fwhole-program -flto=jobserver
-fuse-linker-plugin  -DSPEC_CPU_LP64        changesoplex.o didxset.o dsvector.o
dvector.o enter.o example.o factor.o forest.o idxset.o leave.o lpcolset.o
lprow.o lprowset.o message.o mpsinput.o nameset.o slufactor.o solve.o soplex.o
spxaggregatesm.o spxbasis.o spxbounds.o spxchangebasis.o spxdefaultpr.o
spxdefaultrt.o spxdefines.o spxdesc.o spxdevexpr.o spxequilisc.o spxfastrt.o
spxgeneralsm.o spxharrisrt.o spxhybridpr.o spxid.o spxio.o spxlp.o spxlpfread.o
spxmpsread.o spxmpswrite.o spxparmultpr.o spxquality.o spxredundantsm.o
spxrem1sm.o spxscaler.o spxshift.o spxsolve.o spxsolver.o spxstarter.o
spxsteeppr.o spxsumst.o spxvecs.o spxvectorst.o spxweightpr.o spxweightst.o
ssvector.o svector.o svset.o timer.o unitvector.o update.o updatevector.o
vector.o vsolve.o                     -o soplex
...
 Running 450.soplex ref peak lto default

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


             reply	other threads:[~2015-02-11 20:23 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11 20:23 hjl.tools at gmail dot com [this message]
2015-02-11 20:32 ` [Bug ipa/65028] " hubicka at gcc dot gnu.org
2015-02-12 13:28 ` rguenth at gcc dot gnu.org
2015-02-12 13:41 ` jamborm at gcc dot gnu.org
2015-02-13 17:02 ` jamborm at gcc dot gnu.org
2015-02-13 19:03 ` hubicka at ucw dot cz
2015-02-13 20:05 ` hubicka at gcc dot gnu.org
2015-02-13 20:06 ` hubicka at gcc dot gnu.org
2015-02-13 20:31 ` hubicka at gcc dot gnu.org
2015-02-16 17:35 ` jamborm at gcc dot gnu.org
2015-02-16 17:42 ` hjl.tools at gmail dot com
2015-02-16 18:40 ` hubicka at gcc dot gnu.org
2015-02-16 19:44 ` hjl.tools at gmail dot com
2015-02-16 21:20 ` hubicka at ucw dot cz
2015-02-17 16:23 ` hjl.tools at gmail dot com
2015-02-17 16:41 ` hjl.tools at gmail dot com
2015-02-17 17:03 ` hjl.tools at gmail dot com
2015-02-17 18:07 ` hjl.tools at gmail dot com
2015-02-17 18:14 ` jamborm at gcc dot gnu.org
2015-02-17 18:16 ` hubicka at gcc dot gnu.org
2015-02-17 18:20 ` hjl.tools at gmail dot com
2015-02-17 18:32 ` hjl.tools at gmail dot com
2015-02-17 19:09 ` hjl.tools at gmail dot com
2015-02-17 19:41 ` hjl.tools at gmail dot com
2015-02-17 20:37 ` hjl.tools at gmail dot com
2015-02-17 21:27 ` hjl.tools at gmail dot com
2015-02-17 22:32 ` hjl.tools at gmail dot com
2015-02-17 22:33 ` hjl.tools at gmail dot com
2015-02-17 23:52 ` hjl.tools at gmail dot com
2015-02-17 23:54 ` hubicka at ucw dot cz
2015-02-18 17:13 ` hjl.tools at gmail dot com
2015-02-18 17:32 ` hjl.tools at gmail dot com
2015-02-18 19:33 ` hjl.tools at gmail dot com
2015-02-18 20:09 ` hjl.tools at gmail dot com
2015-02-18 20:19 ` hubicka at ucw dot cz
2015-02-18 21:16 ` hubicka at ucw dot cz
2015-02-18 21:21 ` hjl.tools at gmail dot com
2015-02-18 21:41 ` hubicka at ucw dot cz
2015-02-18 21:41 ` jamborm at gcc dot gnu.org
2015-02-18 21:54 ` hjl.tools at gmail dot com
2015-02-18 21:54 ` hjl.tools at gmail dot com
2015-02-18 22:18 ` jamborm at gcc dot gnu.org
2015-02-18 22:33 ` hjl.tools at gmail dot com
2015-02-18 22:34 ` hjl.tools at gmail dot com
2015-02-18 22:46 ` jamborm at gcc dot gnu.org
2015-02-18 23:11 ` hjl.tools at gmail dot com
2015-02-18 23:11 ` hjl.tools at gmail dot com
2015-02-19 16:36 ` trippels at gcc dot gnu.org
2015-02-19 16:41 ` jamborm at gcc dot gnu.org
2015-02-19 18:46 ` jamborm at gcc dot gnu.org
2015-02-19 19:03 ` jamborm at gcc dot gnu.org
2015-02-19 19:37 ` hjl.tools at gmail dot com
2015-02-19 19:57 ` hubicka at ucw dot cz
2015-02-19 20:06 ` hjl.tools at gmail dot com
2015-02-19 23:32 ` hubicka at gcc dot gnu.org
2015-02-20  6:46 ` hubicka at ucw dot cz
2015-02-20 10:12 ` trippels at gcc dot gnu.org
2015-02-20 13:43 ` jamborm 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-65028-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: 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).