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 middle-end/91512] [10 Regression] Fortran compile time regression.
Date: Tue, 21 Apr 2020 16:45:43 +0000 [thread overview]
Message-ID: <bug-91512-4-ZfVyDah4RD@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 #27 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 21 Apr 2020, tkoenig at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91512
>
> --- Comment #26 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
> (In reply to Bill Seurer from comment #25)
> > This is affecting us on powerpc64 as well. It takes twice as long to build
> > the spec2017 test cases with most of the difference in a few of the fortran
> > compilations which take 30 times or more longer. I tried the new option but
> > it seems to have no effect.
> >
> > Some quick comparison timings:
> >
> > compiling module_first_rk_step_part1.fppized.f90 (part of 521.wrf_r)
> >
> > r10-484: 0m17, 0m14
> > r10-485: 9m19, 9m17
> > r10-7837 (current-ish trunk): 9m57, 10m3
> > r10-7837 with -finline-arg-packing: 9m58, 9m59
> >
> > Compiling all of spec2017
> >
> > r10-484: 34m8
> > r10-485: 65m1
> > r10-7837: 63m47
> > r10-7837 w. option: 65m36
>
> Does the option actually work, i.e. does it have the desired effect
> of not expanding the packing inline? Maybe you could do a quick check
> of the tree dumps generated.
I think you need -fno-inline-arg-packing
next prev parent reply other threads:[~2020-04-21 16:45 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 [this message]
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
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-ZfVyDah4RD@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: link
Be 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).