public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54073] [4.7/4.8 Regression] SciMark Monte Carlo test performance has seriously decreased in recent GCC releases
Date: Tue, 24 Jul 2012 09:23:00 -0000	[thread overview]
Message-ID: <bug-54073-4-Sj0gqnQBha@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54073-4@http.gcc.gnu.org/bugzilla/>

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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-07-24
                 CC|                            |rguenth at gcc dot gnu.org
      Known to work|                            |4.6.4
            Summary|SciMark Monte Carlo test    |[4.7/4.8 Regression]
                   |performance has seriously   |SciMark Monte Carlo test
                   |decreased in recent GCC     |performance has seriously
                   |releases                    |decreased in recent GCC
                   |                            |releases
     Ever Confirmed|0                           |1
      Known to fail|                            |4.7.0, 4.8.0

--- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-07-24 09:22:45 UTC ---
Our autotesters have a jump of this magnitude between

K8:   good r171332, bad r171367
K10:  good r171399, bad r171360
IA64: good r182218, bad r182265

needs further bisection, there are a few candidates within the 171399:171360
range.  IA64 is supposedly sth else (the fix for PR21617 pops up here).

Confirmed at least.


  parent reply	other threads:[~2012-07-24  9:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23 15:25 [Bug tree-optimization/54073] New: " t.artem at mailcity dot com
2012-07-23 15:44 ` [Bug tree-optimization/54073] " t.artem at mailcity dot com
2012-07-24  9:23 ` rguenth at gcc dot gnu.org [this message]
2012-07-24 11:29 ` [Bug tree-optimization/54073] [4.7/4.8 Regression] " markus at trippelsdorf dot de
2012-07-24 13:21 ` rguenth at gcc dot gnu.org
2012-07-26 15:41 ` venkataramanan.kumar at amd dot com
2012-07-26 16:13 ` markus at trippelsdorf dot de
2012-08-16 11:06 ` rguenth at gcc dot gnu.org
2012-09-07 10:09 ` rguenth at gcc dot gnu.org
2012-09-20 10:28 ` jakub at gcc dot gnu.org
2012-11-13 13:05 ` jakub at gcc dot gnu.org
2012-11-13 15:07 ` t.artem at mailcity dot com
2012-11-13 15:14 ` ubizjak at gmail dot com
2012-11-13 15:24 ` jakub at gcc dot gnu.org
2012-11-13 15:55 ` hubicka at gcc dot gnu.org
2012-11-16 11:41 ` jakub at gcc dot gnu.org
2012-11-16 14:50 ` [Bug tree-optimization/54073] [4.7 " jakub at gcc dot gnu.org
2012-12-31  9:41 ` pinskia at gcc dot gnu.org
2013-02-16 19:12 ` jake.stine at gmail dot com
2013-02-17  8:41 ` ubizjak at gmail dot com
2013-04-11  7:59 ` rguenth at gcc dot gnu.org
2014-06-12 13:16 ` 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-54073-4-Sj0gqnQBha@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).