public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/110489] Slow building virtual.c.i from p11-kit Date: Fri, 30 Jun 2023 08:38:28 +0000 [thread overview] Message-ID: <bug-110489-4-Ca5MYmyPIf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110489-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110489 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:18e5aeaef294428fc8458c2c70a9ac3a537c35d6 commit r14-2209-g18e5aeaef294428fc8458c2c70a9ac3a537c35d6 Author: Richard Biener <rguenther@suse.de> Date: Fri Jun 30 09:46:48 2023 +0200 middle-end/110489 - avoid useless work on statistics When we call statistics_fini_pass we unconditionally allocate the statistics hash and traverse it. When a TU has many small functions this can take considerable time. The following avoids this by never allocating the hash from this function. PR middle-end/110489 * statistics.cc (curr_statistics_hash): Add argument indicating whether we should allocate the hash. (statistics_fini_pass): If the hash isn't allocated only print the summary header.
prev parent reply other threads:[~2023-06-30 8:38 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-29 19:35 [Bug c/110489] New: " sjames at gcc dot gnu.org 2023-06-29 19:46 ` [Bug middle-end/110489] " pinskia at gcc dot gnu.org 2023-06-29 19:54 ` pinskia at gcc dot gnu.org 2023-06-30 7:45 ` rguenth at gcc dot gnu.org 2023-06-30 8:37 ` rguenth at gcc dot gnu.org 2023-06-30 8:38 ` cvs-commit 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-110489-4-Ca5MYmyPIf@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).