public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/59487] [4.9 Regression] When compiled with -fwhole-program rnflow.f90 runs up to 40% slower after r202826 Date: Thu, 27 Feb 2014 10:56:00 -0000 [thread overview] Message-ID: <bug-59487-4-R9JYB95SCG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59487-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59487 --- Comment #8 from rguenther at suse dot de <rguenther at suse dot de> --- On Thu, 27 Feb 2014, Ganesh.Gopalasubramanian at amd dot com wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59487 > > --- Comment #7 from GGanesh <Ganesh.Gopalasubramanian at amd dot com> --- > Richard! With gcc version 4.9.0 20140224, I could see a gap between > with/without -fwhole-program. With what other options? > with -fwhole-program : time ./rnflowWhPr > real 0m26.184s > user 0m26.018s > sys 0m0.156s > > without -fwhole-program: time ./rnflow > real 0m18.251s > user 0m18.061s > sys 0m0.180s
next prev parent reply other threads:[~2014-02-27 10:56 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-12 18:19 [Bug tree-optimization/59487] New: " dominiq at lps dot ens.fr 2013-12-13 9:28 ` [Bug tree-optimization/59487] " rguenth at gcc dot gnu.org 2013-12-13 9:51 ` burnus at gcc dot gnu.org 2013-12-13 13:03 ` dominiq at lps dot ens.fr 2013-12-13 14:01 ` rguenther at suse dot de 2013-12-13 14:14 ` dominiq at lps dot ens.fr 2014-02-27 9:25 ` rguenth at gcc dot gnu.org 2014-02-27 10:09 ` Ganesh.Gopalasubramanian at amd dot com 2014-02-27 10:56 ` rguenther at suse dot de [this message] 2014-02-27 15:35 ` Ganesh.Gopalasubramanian at amd dot com 2014-03-18 11:39 ` jakub at gcc dot gnu.org 2014-03-18 14:56 ` 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-59487-4-R9JYB95SCG@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: linkBe 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).