public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104581] [12 Regression] Huge compile-time regression building SPEC 2017 538.imagick_r with PGO
Date: Thu, 17 Feb 2022 13:03:07 +0000	[thread overview]
Message-ID: <bug-104581-4-02O3WAsVWD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104581-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Ah, you're right.
So, can't it instead of the quadratic walk just compare DF_INSN_LUID?
If it isn't right after df_analyze and some insns could have been added in
between, it would need to maintain the luids somehow (perhaps e.g. in the way
how we do it in tree-ssa-reassoc.cc, if we add insns, we must set their uid to
either the previous or next insn's uid and then can do some IL walk, but only
as long as the uid is the same, so unless everything in the bb changes it
should be still cheap.

  parent reply	other threads:[~2022-02-17 13:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 11:33 [Bug target/104581] New: " rguenth at gcc dot gnu.org
2022-02-17 11:33 ` [Bug target/104581] [12 Regression] " rguenth at gcc dot gnu.org
2022-02-17 11:47 ` rguenth at gcc dot gnu.org
2022-02-17 11:56 ` rguenth at gcc dot gnu.org
2022-02-17 12:35 ` rguenth at gcc dot gnu.org
2022-02-17 12:43 ` rguenth at gcc dot gnu.org
2022-02-17 12:54 ` jakub at gcc dot gnu.org
2022-02-17 12:57 ` rguenth at gcc dot gnu.org
2022-02-17 13:03 ` jakub at gcc dot gnu.org [this message]
2022-02-17 13:04 ` jakub at gcc dot gnu.org
2022-02-17 13:11 ` rguenther at suse dot de
2022-02-18  7:50 ` cvs-commit at gcc dot gnu.org
2022-02-18  7:51 ` rguenth at gcc dot gnu.org
2022-02-18 18:41 ` 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-104581-4-02O3WAsVWD@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).