public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/44334] rnflow.f90 ~27% slower with -fwhole-program -flto after revision 159852 Date: Thu, 09 Sep 2010 09:01:00 -0000 [thread overview] Message-ID: <20100909090046.21056.qmail@sourceware.org> (raw) In-Reply-To: <bug-44334-12313@http.gcc.gnu.org/bugzilla/> ------- Comment #11 from burnus at gcc dot gnu dot org 2010-09-09 09:00 ------- [Move comment from IRC #gcc to bugzilla] (In reply to comment #9) > For what it is worth, on AMD Athlon 64 X2 4800+ / x86-64-linux, [...] > That's a +16% increase in run-time with -fwhole-program. (In reply to comment #10) > So hot-bb-frequency-fraction solves the whole regression? For me (cf. system above), --param hot-bb-frequency-fraction=2000 reduces the slow down due to -fwhole-program from 16% to 3%. (The LTO version with and without -fwhole-file is about 2% slower than the corresponding -fno-lto version.) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44334
prev parent reply other threads:[~2010-09-09 9:01 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-05-30 17:17 [Bug lto/44334] New: [4.6 Regression] " dominiq at lps dot ens dot fr 2010-05-30 18:06 ` [Bug lto/44334] " dominiq at lps dot ens dot fr 2010-05-30 18:09 ` [Bug fortran/44334] " rguenth at gcc dot gnu dot org 2010-05-30 18:11 ` dominiq at lps dot ens dot fr 2010-05-30 18:12 ` dominiq at lps dot ens dot fr 2010-05-30 18:31 ` dominiq at lps dot ens dot fr 2010-05-30 18:49 ` rguenth at gcc dot gnu dot org 2010-05-30 18:55 ` dominiq at lps dot ens dot fr 2010-06-05 9:52 ` dominiq at lps dot ens dot fr 2010-09-08 21:00 ` burnus at gcc dot gnu dot org 2010-09-08 21:04 ` hubicka at gcc dot gnu dot org 2010-09-09 9:01 ` burnus at gcc dot gnu dot org [this message]
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=20100909090046.21056.qmail@sourceware.org \ --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).