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 middle-end/64099] New: [5 Regression] ~15% runtime increase for fatigue.f90. Date: Fri, 28 Nov 2014 10:47:00 -0000 [thread overview] Message-ID: <bug-64099-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64099 Bug ID: 64099 Summary: [5 Regression] ~15% runtime increase for fatigue.f90. Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: dominiq at lps dot ens.fr CC: hubicka at ucw dot cz, rguenth at gcc dot gnu.org On x86_64-apple-darwin14, I see a ~15% runtime increase for the polyhedron test fatigue.f90 on the current trunk (r218134). It is split in two steps. The first one occurred between r216631 and r216747: [Book15] lin/test% /opt/gcc/gcc4.10p-216631p3/bin/gfortran -fprotect-parens -Ofast -funroll-loops -ftree-loop-linear -fomit-frame-pointer -fwhole-program -flto fatigue.f90 [Book15] lin/test% time a.out > /dev/null 1.373u 0.001s 0:01.37 100.0% 0+0k 0+0io 0pf+0w [Book15] lin/test% /opt/gcc/gcc4.10p-216747p2/bin/gfortran -fprotect-parens -Ofast -funroll-loops -ftree-loop-linear -fomit-frame-pointer -fwhole-program -flto fatigue.f90 [Book15] lin/test% time a.out > /dev/null 1.462u 0.002s 0:01.47 99.3% 0+0k 0+1io 40pf+0w The second one occurred between r217816 and r217833: [Book15] lin/test% /opt/gcc/gcc4.10p-217816p2/bin/gfortran -fprotect-parens -Ofast -funroll-loops -ftree-loop-linear -fomit-frame-pointer -fwhole-program -flto fatigue.f90 [Book15] lin/test% time a.out > /dev/null 1.435u 0.002s 0:01.44 99.3% 0+0k 0+2io 41pf+0w [Book15] lin/test% /opt/gcc/gcc4.10p-217833p1/bin/gfortran -fprotect-parens -Ofast -funroll-loops -ftree-loop-linear -fomit-frame-pointer -fwhole-program -flto fatigue.f90 [Book15] lin/test% time a.out > /dev/null 1.582u 0.001s 0:01.58 100.0% 0+0k 0+1io 0pf+0w
next reply other threads:[~2014-11-28 10:47 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-28 10:47 dominiq at lps dot ens.fr [this message] 2014-11-28 11:03 ` [Bug middle-end/64099] " rguenth at gcc dot gnu.org 2014-11-28 11:03 ` rguenth at gcc dot gnu.org 2014-11-28 13:16 ` rguenth at gcc dot gnu.org 2014-11-28 14:03 ` dominiq at lps dot ens.fr 2014-11-28 15:54 ` dominiq at lps dot ens.fr 2014-11-28 19:37 ` dominiq at lps dot ens.fr 2014-12-11 13:58 ` rguenth at gcc dot gnu.org 2014-12-11 15:02 ` rguenth at gcc dot gnu.org 2015-01-15 11:42 ` rguenth at gcc dot gnu.org 2015-01-15 12:32 ` dominiq at lps dot ens.fr 2015-03-03 16:02 ` law at redhat dot com 2015-04-15 9:47 ` [Bug middle-end/64099] [5/6 " dominiq at lps dot ens.fr 2015-04-15 11:24 ` dominiq at lps dot ens.fr 2015-04-15 13:15 ` dominiq at lps dot ens.fr 2015-04-22 12:02 ` jakub at gcc dot gnu.org 2015-07-16 9:20 ` rguenth at gcc dot gnu.org 2021-05-14 9:47 ` [Bug middle-end/64099] [9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:06 ` rguenth at gcc dot gnu.org 2022-05-27 9:35 ` [Bug middle-end/64099] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:31 ` jakub at gcc dot gnu.org 2023-07-07 10:30 ` [Bug middle-end/64099] [11/12/13/14 " 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-64099-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).