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 middle-end/110489] Slow building virtual.c.i from p11-kit
Date: Fri, 30 Jun 2023 07:45:30 +0000	[thread overview]
Message-ID: <bug-110489-4-BRzzWsmZ4N@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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2023-06-30
           Assignee|unassigned at gcc dot gnu.org      |rguenth at gcc dot gnu.org

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Samples: 45K of event 'cycles', Event count (approx.): 51356148788              
Overhead       Samples  Command  Shared Object       Symbol                     
   2.57%          1169  cc1      libc-2.31.so        [.] _int_malloc
   1.54%           700  cc1      cc1                 [.] bitmap_set_bit
   1.52%           692  cc1      libc-2.31.so        [.] malloc
   1.32%           602  cc1      libc-2.31.so        [.] _int_free
   1.31%           598  cc1      cc1                 [.] record_reg_classes
   1.04%           476  cc1      cc1                 [.] constrain_operands
   0.81%           368  cc1      cc1                 [.] solve_constraints
   0.79%           360  cc1      cc1                 [.] cse_insn
   0.78%           357  cc1      cc1                 [.] ggc_internal_alloc
   0.76%           347  cc1      libc-2.31.so        [.] free
   0.73%           330  cc1      cc1                 [.] statistics_fini_pass

it's pointing at things I've seen multiple times, but I think investigating
why memory allocation is so high up in the profile would be good.  There
are some users like dom_info::dom_init which hit hard on the allocator
without good reason but then it's only few per function but as seen this
testcase has many of them.  Likewise ipa_sra_summarize_function seems to
have 99% cost in memory allocation.  Doing more on-demand initialization
might help here.

I have a patch for the statistics_finish_pass hit.

  parent reply	other threads:[~2023-06-30  7:45 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 [this message]
2023-06-30  8:37 ` rguenth at gcc dot gnu.org
2023-06-30  8:38 ` cvs-commit 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-110489-4-BRzzWsmZ4N@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).