public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/79966] [9/10/11 Regression] Test gfortran.dg/pr79966.f90 slow again, inliner hits max-inline-insns-auto
Date: Thu, 07 Jan 2021 16:20:52 +0000 [thread overview]
Message-ID: <bug-79966-4-VVnIGqK5p6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-79966-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79966
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[9/10/11 Regression] run |[9/10/11 Regression] Test
|time more than twice slower |gfortran.dg/pr79966.f90
|when using -fipa-cp-clone |slow again, inliner hits
| |max-inline-insns-auto
--- Comment #14 from Martin Jambor <jamborm at gcc dot gnu.org> ---
And if I looked into the testcase that is in the repo, I would have
discovered PR 88711 which is exactly about this. See Honza's comments
about the problem there.
(I'd prefer to keep that bug opened and close this one, but Honza
decided otherwise, so I'm changing the name because it not an IPA-CP
issue any more).
next prev parent reply other threads:[~2021-01-07 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-79966-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 11:58 ` [Bug ipa/79966] [9/10 Regression] run time more than twice slower when using -fipa-cp-clone jakub at gcc dot gnu.org
2021-01-07 15:53 ` [Bug ipa/79966] [9/10/11 " jamborm at gcc dot gnu.org
2021-01-07 16:20 ` jamborm at gcc dot gnu.org [this message]
2021-06-01 8:08 ` [Bug ipa/79966] [9/10/11/12 Regression] Test gfortran.dg/pr79966.f90 slow again, inliner hits max-inline-insns-auto rguenth at gcc dot gnu.org
2022-05-27 9:37 ` [Bug ipa/79966] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:33 ` jakub at gcc dot gnu.org
2023-07-07 10:32 ` [Bug ipa/79966] [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-79966-4-VVnIGqK5p6@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).