public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/91512] [10 Regression] Fortran compile time regression. Date: Thu, 23 Apr 2020 19:47:41 +0000 [thread overview] Message-ID: <bug-91512-4-AeekNf3u7s@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-91512-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91512 --- Comment #31 from Michael Meissner <meissner at gcc dot gnu.org> --- For the Spec 2017 521.wrf_r benchmark on little endian PowerPC power9 systems, there was no difference in runtime between a normal run using -Ofast -mcpu=power9 and one with -Ofast -mcpu=power9 -fno-inline-arg-packing. Of the seven rate benchmarks in Spec 2017 that use Fortran (548.exchange2_r, 503.bwaves_r, 507.cactuBSSN_r, 521.wrf_r, 527.cam4_r, 549.fotonik3d_r, and 554.roms_r) none of them vary by more tha 0.7% depending on whether the switch is used or not. I used the compiler checked out from the master branch on March 27, 2020 to build and run the benchmarks. As others have said, using -fno-inline-arg-packing does dramatically reduce the time it takes to compile 521.wrf_r.
next prev parent reply other threads:[~2020-04-23 19:47 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-91512-4@http.gcc.gnu.org/bugzilla/> 2020-04-21 16:00 ` seurer at linux dot vnet.ibm.com 2020-04-21 16:33 ` tkoenig at gcc dot gnu.org 2020-04-21 16:45 ` rguenther at suse dot de 2020-04-21 17:33 ` rguenth at gcc dot gnu.org 2020-04-22 3:54 ` seurer at linux dot vnet.ibm.com 2020-04-22 14:48 ` seurer at linux dot vnet.ibm.com 2020-04-23 19:47 ` meissner at gcc dot gnu.org [this message] 2020-05-07 11:56 ` [Bug middle-end/91512] [10/11 " jakub at gcc dot gnu.org 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2022-06-28 10:38 ` [Bug middle-end/91512] [10/11/12/13 " jakub at gcc dot gnu.org 2023-07-07 10:35 ` [Bug middle-end/91512] [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-91512-4-AeekNf3u7s@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).