public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/40979] induct benchmark 60% slower when compiled with -fgraphite-identity
Date: Wed, 26 Jan 2011 14:43:00 -0000	[thread overview]
Message-ID: <bug-40979-4-6LozMptBNh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-40979-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Jack Howarth <howarth at nitro dot med.uc.edu> 2011-01-26 14:20:18 UTC ---
(In reply to comment #9)
> This pr is not fixed at revision 169261 (gfc). AFAIU -ftree-loop-linear is now
> implemented through graphite. This leads to a sort of regression with respect
> to revision 169227(gfc6):
> 
> [macbook] lin/test% gfc -Ofast -ftree-loop-linear induct.f90
> [macbook] lin/test% time a.out > /dev/null
> 22.380u 0.023s 0:22.40 100.0%    0+0k 0+0io 0pf+0w
> [macbook] lin/test% gfc6 -Ofast -ftree-loop-linear induct.f90
> [macbook] lin/test% time a.out > /dev/null
> 13.978u 0.019s 0:13.99 99.9%    0+0k 0+0io 0pf+0w

Note that -fgraphite-identity still triggers a large number of failures in the
vect.exp testsuite when defaulted on at -O2...

http://gcc.gnu.org/ml/gcc-testresults/2011-01/msg02005.html

so the regression in induct.f90 isn't unique.


  parent reply	other threads:[~2011-01-26 14:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-40979-4@http.gcc.gnu.org/bugzilla/>
2011-01-26 10:45 ` dominiq at lps dot ens.fr
2011-01-26 14:43 ` howarth at nitro dot med.uc.edu [this message]
2011-01-31 18:53 ` spop at gcc dot gnu.org
2011-01-31 19:36 ` dominiq at lps dot ens.fr
2011-02-01 11:35 ` rguenth at gcc dot gnu.org
2011-02-01 11:45 ` rguenth at gcc dot gnu.org
2011-02-01 16:47 ` spop at gcc dot gnu.org
2011-02-01 17:18 ` rguenth at gcc dot gnu.org
2011-02-01 17:23 ` sebpop at gmail dot com
2011-02-01 17:51 ` sebpop at gmail dot com
2011-02-01 18:22 ` dominiq at lps dot ens.fr
2011-02-01 21:19 ` howarth at nitro dot med.uc.edu
2011-02-01 21:22 ` spop at gcc dot gnu.org
2011-02-02 15:53 ` spop at gcc dot gnu.org
2011-02-02 15:59 ` spop at gcc dot gnu.org
2009-08-06  0:19 [Bug middle-end/40979] New: " howarth at nitro dot med dot uc dot edu
2009-08-06  0:23 ` [Bug middle-end/40979] " spop at gcc dot gnu dot org
2009-08-12 14:58 ` spop at gcc dot gnu dot org
2009-08-13  2:26 ` howarth at nitro dot med dot uc dot edu
2009-08-14 11:59 ` dominiq at lps dot ens dot fr
2009-12-14 19:24 ` spop at gcc dot gnu dot org
2010-02-25 15:23 ` dominiq at lps dot ens dot fr
2010-02-25 17:26 ` dominiq at lps dot ens dot fr
2010-03-10  1:57 ` howarth at nitro dot med dot uc dot edu
2010-03-15 14:21 ` dominiq at lps dot ens dot fr

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-40979-4-6LozMptBNh@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).