public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109143] PTA compile-time hog with many calls
Date: Mon, 19 Feb 2024 13:51:40 +0000	[thread overview]
Message-ID: <bug-109143-4-3virnJ6zbO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109143-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109143

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2023-03-15 00:00:00         |2024-2-19

--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
With GCC 14 at -O1:

 template instantiation             :   0.90 (  8%)
 tree PTA                           :   0.51 (  5%)
 TOTAL                              :  11.14 

and with -O2:

 callgraph ipa passes               :   5.76 ( 19%)
 tree PTA                           :   9.42 ( 31%)
 integrated RA                      :   1.79 (  6%)
 TOTAL                              :  30.72

      parent reply	other threads:[~2024-02-19 13:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 12:39 [Bug tree-optimization/109143] New: " rguenth at gcc dot gnu.org
2023-03-15 12:44 ` [Bug tree-optimization/109143] " rguenth at gcc dot gnu.org
2023-05-31 11:27 ` cvs-commit at gcc dot gnu.org
2023-05-31 12:33 ` rguenth at gcc dot gnu.org
2023-06-06  8:30 ` cvs-commit at gcc dot gnu.org
2023-06-23 10:29 ` cvs-commit at gcc dot gnu.org
2023-11-27 11:34 ` cvs-commit at gcc dot gnu.org
2024-02-19 13:51 ` rguenth at gcc dot gnu.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=bug-109143-4-3virnJ6zbO@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).