public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/108130] New: [13 Regression] LTO compile time hog seen on bootstrap-lto config since r13-4684-g7450b25566b7a7
Date: Thu, 15 Dec 2022 15:47:05 +0000	[thread overview]
Message-ID: <bug-108130-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 108130
           Summary: [13 Regression] LTO compile time hog seen on
                    bootstrap-lto config since r13-4684-g7450b25566b7a7
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Keywords: compile-time-hog
          Severity: normal
          Priority: P3
         Component: ipa
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: jamborm at gcc dot gnu.org, marxin at gcc dot gnu.org
  Target Milestone: ---

I noticed linking of e.g. cc1plus gets much slower in stage2 with a WPA hog in:

    58.15%  lto1                [.] lto_symtab_encoder_lookup
    19.95%  lto1                [.] may_need_named_section_p
    18.77%  lto1                [.] rename_statics
     0.50%  lto1                [.] lto_symtab_encoder_lookup
     0.09%  lto1                [.] lto_symtab_encoder_encode_body_p

The WPA phase takes >5 minutes, while it used to take ~30 seconds on my
machine.

             reply	other threads:[~2022-12-15 15:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 15:47 marxin at gcc dot gnu.org [this message]
2022-12-15 15:48 ` [Bug ipa/108130] " marxin at gcc dot gnu.org
2022-12-16 12:00 ` rguenth at gcc dot gnu.org
2022-12-19 12:03 ` marxin at gcc dot gnu.org
2022-12-21 10:57 ` marxin at gcc dot gnu.org
2023-01-05 16:11 ` jamborm 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-108130-4@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).