public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/59487] New: [4.9 Regression] When compiled with -fwhole-program rnflow.f90 runs up to 40% slower after r202826 Date: Thu, 12 Dec 2013 18:19:00 -0000 [thread overview] Message-ID: <bug-59487-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59487 Bug ID: 59487 Summary: [4.9 Regression] When compiled with -fwhole-program rnflow.f90 runs up to 40% slower after r202826 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: dominiq at lps dot ens.fr CC: burnus at gcc dot gnu.org, Ganesh.Gopalasubramanian at amd dot com, rguenth at gcc dot gnu.org When compiled with -fwhole-program rnflow.f90 runs up to 40% slower after r202826 (Core i7 at 2.8Ghz): [Book15] lin/test% /opt/gcc/gcc4.9p-202828/bin/gfortran -Ofast -fwhole-program rnflow.f90 [Book15] lin/test% time a.out > /dev/null 18.244u 0.020s 0:18.26 100.0% 0+0k 3+1io 0pf+0w [Book15] lin/test% /opt/gcc/gcc4.9p-202825/bin/gfortran -Ofast -fwhole-program rnflow.f90 [Book15] lin/test% time a.out > /dev/null 13.022u 0.024s 0:13.04 100.0% 0+0k 4+1io 0pf+0w [Book15] lin/test% gfcc -Ofast -fwhole-program rnflow.f90 [Book15] lin/test% time a.out > /dev/null 18.533u 0.036s 0:18.58 99.8% 0+0k 0+0io 45pf+0w [Book15] lin/test% gfcc -Ofast rnflow.f90 [Book15] lin/test% time a.out > /dev/null 13.059u 0.020s 0:13.08 99.9% 0+0k 0+0io 0pf+0w [Book15] lin/test% gfc -Ofast -fwhole-program rnflow.f90 [Book15] lin/test% time a.out > /dev/null 12.940u 0.028s 0:12.97 99.9% 0+0k 0+0io 14pf+0w gfcc is r205891 and gfc r205924 with the patch for pr58721 at http://gcc.gnu.org/ml/fortran/2013-12/msg00069.html which fixes also this slowdown (the slowdown is ~20% on a Core2Duo at 2.5Ghz). This has been noticed in the last comment of pr58464.
next reply other threads:[~2013-12-12 18:19 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-12 18:19 dominiq at lps dot ens.fr [this message] 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 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@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).