public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/53342] [4.8 Regression] rnflow.f90 is ~5% slower after revision 187340
Date: Mon, 14 Jan 2013 16:45:00 -0000	[thread overview]
Message-ID: <bug-53342-4-jQFGtdj7Z5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53342-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-01-14 16:45:11 UTC ---
Can't we then compute the final values of the bases after the peeling loop, and
add those gimplified after the peeling loop, then use them in the next loop?


  parent reply	other threads:[~2013-01-14 16:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 11:43 [Bug tree-optimization/53342] New: " dominiq at lps dot ens.fr
2012-05-14 11:49 ` [Bug tree-optimization/53342] " rguenth at gcc dot gnu.org
2012-05-14 12:33 ` matz at gcc dot gnu.org
2012-09-07 11:51 ` rguenth at gcc dot gnu.org
2012-11-13 18:46 ` ubizjak at gmail dot com
2012-12-10 12:11 ` jakub at gcc dot gnu.org
2012-12-10 12:26 ` rguenther at suse dot de
2013-01-11 11:53 ` jakub at gcc dot gnu.org
2013-01-14 15:56 ` matz at gcc dot gnu.org
2013-01-14 16:45 ` jakub at gcc dot gnu.org [this message]
2013-02-05 12:12 ` rguenth at gcc dot gnu.org
2013-02-05 13:08 ` rguenth at gcc dot gnu.org
2013-02-05 13:36 ` dominiq at lps dot ens.fr
2013-02-05 13:52 ` rguenth at gcc dot gnu.org
2013-02-05 15:34 ` rguenth at gcc dot gnu.org
2013-02-05 15:36 ` 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-53342-4-jQFGtdj7Z5@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).