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 tree-optimization/108697] constructing a path-range-query is expensive
Date: Tue, 07 Feb 2023 14:34:02 +0000 [thread overview]
Message-ID: <bug-108697-4-gIlZBnA8fg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108697-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108697
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
But yes, your observation about m_has_cache_entry is correct - if that has any
value (it makes reset_path "cheap"), then it should be also relied on upon
growth. Maybe make this bitmap an optional feature of the cache itself
and handle it transparently there?
next prev parent reply other threads:[~2023-02-07 14:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 13:31 [Bug tree-optimization/108697] New: " rguenth at gcc dot gnu.org
2023-02-07 14:13 ` [Bug tree-optimization/108697] " aldyh at gcc dot gnu.org
2023-02-07 14:31 ` rguenth at gcc dot gnu.org
2023-02-07 14:34 ` rguenth at gcc dot gnu.org [this message]
2023-02-07 15:03 ` aldyh at gcc dot gnu.org
2023-02-07 19:52 ` aldyh at gcc dot gnu.org
2023-02-10 2:54 ` amacleod at redhat dot com
2023-04-26 19:26 ` cvs-commit at gcc dot gnu.org
2023-10-11 19:51 ` amacleod at redhat dot com
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-108697-4-gIlZBnA8fg@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).