public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104203] [12 Regressions] huge compile-time regression since r12-6606-g9d6a0f388eb048f8
Date: Mon, 24 Jan 2022 20:22:50 +0000	[thread overview]
Message-ID: <bug-104203-4-TzjQEVWo9v@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104203-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Martin Sebor <msebor at gcc dot gnu.org> ---
The underlying problem is that when the pointer_query class fails to determine
the pointer provenance for an SSA variable it doesn't update the cache, matter
how laborious the computation was.  The next time the same SSA variable is
seen, the query goes through the same computation only to eventually fail
again.  Caching a permissive result instead of failing short-circuits this
process and avoids the bottleneck.

  parent reply	other threads:[~2022-01-24 20:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 11:31 [Bug ipa/104203] New: [12 Regressions] huge IPA compile-time regression rguenth at gcc dot gnu.org
2022-01-24 11:33 ` [Bug ipa/104203] " rguenth at gcc dot gnu.org
2022-01-24 11:34 ` rguenth at gcc dot gnu.org
2022-01-24 11:36 ` rguenth at gcc dot gnu.org
2022-01-24 12:01 ` [Bug ipa/104203] [12 Regressions] huge IPA compile-time regression since r12-6606-g9d6a0f388eb048f8 marxin at gcc dot gnu.org
2022-01-24 12:14   ` Jan Hubicka
2022-01-24 12:14 ` hubicka at kam dot mff.cuni.cz
2022-01-24 12:26 ` rguenth at gcc dot gnu.org
2022-01-24 12:30 ` rguenth at gcc dot gnu.org
2022-01-24 15:26 ` [Bug tree-optimization/104203] [12 Regressions] huge " msebor at gcc dot gnu.org
2022-01-24 18:09 ` msebor at gcc dot gnu.org
2022-01-24 18:54   ` Jan Hubicka
2022-01-24 18:54 ` hubicka at kam dot mff.cuni.cz
2022-01-24 20:22 ` msebor at gcc dot gnu.org [this message]
2022-01-24 22:57 ` [Bug tree-optimization/104203] [12 Regressions] huge compile-time regression in pointer_query " msebor at gcc dot gnu.org
2022-01-25 21:23 ` cvs-commit at gcc dot gnu.org
2022-01-25 21:29 ` msebor at gcc dot gnu.org
2022-01-27  8:06 ` rguenth 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-104203-4-TzjQEVWo9v@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).