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 ipa/99785] Awful lot of time spent building gl.cc in Firefox
Date: Fri, 26 Mar 2021 10:11:57 +0000 [thread overview]
Message-ID: <bug-99785-4-HzvV9Cmkx5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99785-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99785
--- Comment #12 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #11)
> Btw, GCC 10 branch tip with -O1:
>
> ipa inlining heuristics : 962.91 ( 85%) 0.39 ( 4%) 971.66 (
> 84%) 1103801 kB ( 10%)
> alias stmt walking : 40.95 ( 4%) 1.07 ( 11%) 42.13 (
> 4%) 25965 kB ( 0%)
> integration : 13.66 ( 1%) 3.23 ( 33%) 16.18 (
> 1%) 4931059 kB ( 43%)
> TOTAL :1135.79 9.69 1153.79
> 11462287 kB
> 1135.79user 9.73system 19:13.82elapsed 99%CPU (0avgtext+0avgdata
> 4090216maxresident)k
> 0inputs+0outputs (0major+959014minor)pagefaults 0swaps
And a profile of trunk with release checking shows
Samples: 4M of event 'cycles:u', Event count (approx.): 4811472248176
Overhead Samples Command Shared Object Symbol
31.07% 1371974 cc1plus cc1plus [.] update_callee_keys
25.52% 1128500 cc1plus cc1plus [.] edge_badness
4.91% 216874 cc1plus cc1plus [.]
evaluate_properties_for_edge
3.90% 172368 cc1plus cc1plus [.]
cgraph_node::get_availability
3.83% 169169 cc1plus cc1plus [.] do_estimate_edge_time
2.56% 113399 cc1plus cc1plus [.]
symtab_node::ultimate_alias_target_1
I wonder why we even run into this for the always inlines.
next prev parent reply other threads:[~2021-03-26 10:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 7:57 [Bug c++/99785] New: " mh+gcc at glandium dot org
2021-03-26 8:26 ` [Bug c++/99785] " pinskia at gcc dot gnu.org
2021-03-26 8:27 ` pinskia at gcc dot gnu.org
2021-03-26 8:29 ` pinskia at gcc dot gnu.org
2021-03-26 8:33 ` [Bug ipa/99785] " mh+gcc at glandium dot org
2021-03-26 8:41 ` pinskia at gcc dot gnu.org
2021-03-26 8:49 ` mh+gcc at glandium dot org
2021-03-26 9:08 ` mh+gcc at glandium dot org
2021-03-26 9:27 ` pinskia at gcc dot gnu.org
2021-03-26 9:29 ` jakub at gcc dot gnu.org
2021-03-26 9:33 ` rguenth at gcc dot gnu.org
2021-03-26 9:35 ` rguenth at gcc dot gnu.org
2021-03-26 10:11 ` rguenth at gcc dot gnu.org [this message]
2021-03-26 11:16 ` rguenth at gcc dot gnu.org
2021-03-26 19:31 ` jmuizelaar at mozilla dot com
2021-03-26 21:38 ` hubicka at gcc dot gnu.org
2021-03-26 22:13 ` hubicka at gcc dot gnu.org
2021-03-31 13:32 ` rguenth at gcc dot gnu.org
2021-03-31 13:37 ` jakub at gcc dot gnu.org
2021-05-21 7:29 ` rguenth at gcc dot gnu.org
2021-05-21 9:35 ` rguenth at gcc dot gnu.org
2022-05-17 11:26 ` asolokha at gmx dot com
2022-05-17 15:09 ` jmuizelaar at mozilla dot com
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-99785-4-HzvV9Cmkx5@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).