public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/111241] Extraordinary amount of time spent in "callgraph functions expansion" Date: Wed, 30 Aug 2023 16:58:38 +0000 [thread overview] Message-ID: <bug-111241-4-uexhT41FtN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111241-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111241 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- With -fno-checking but still the default --enable-checking setting for the trunk: alias stmt walking : 18.90 ( 21%) 0.20 ( 7%) 25.86 ( 24%) 8960 ( 0%) df reaching defs : 9.96 ( 11%) 0.05 ( 2%) 9.90 ( 9%) 0 ( 0%) tree FRE : 9.07 ( 10%) 0.38 ( 13%) 9.49 ( 9%) 14M ( 3%) tree DSE : 9.43 ( 11%) 0.00 ( 0%) 9.45 ( 9%) 11k ( 0%) The rest are spread out. Note "callgraph functions expansion" is a "meta" timevar and includes the above really.
next prev parent reply other threads:[~2023-08-30 16:58 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-30 16:31 [Bug c/111241] New: " dcb314 at hotmail dot com 2023-08-30 16:58 ` pinskia at gcc dot gnu.org [this message] 2023-08-31 9:57 ` [Bug middle-end/111241] " rguenth at gcc dot gnu.org 2023-08-31 13:06 ` 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-111241-4-uexhT41FtN@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).