public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108696] querying relations is slow
Date: Fri, 10 Feb 2023 14:53:22 +0000	[thread overview]
Message-ID: <bug-108696-4-vIa6nRGTi9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108696-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Andrew Macleod <amacleod at redhat dot com> ---
(In reply to Richard Biener from comment #4)

> 
> That said, not allocating the self-relation bitmaps at query time is
> definitely good (not 100% sure if the patch achieves that).

 If it can determine ahead of time that it isn't needed, then the self maps do
not get allocated. If it actually has to do a query, then they are allocated.

Im still looking around at this... It was simpler to always do bitmap vs bitmap
comparison rather than the full set of combinations.  Figured I would revisit
it if it was a performance concern.  I will experiment with what happens if we
expand the API, at least internally, to do ssa vs ssa, bitmap vs bitmap, and
ssa vs bitmap checks.

      parent reply	other threads:[~2023-02-10 14:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 13:00 [Bug tree-optimization/108696] New: " rguenth at gcc dot gnu.org
2023-02-08 17:16 ` [Bug tree-optimization/108696] " amacleod at redhat dot com
2023-02-08 17:50 ` amacleod at redhat dot com
2023-02-08 18:01 ` rguenther at suse dot de
2023-02-10  8:38 ` rguenth at gcc dot gnu.org
2023-02-10 14:53 ` amacleod at redhat dot com [this message]

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-108696-4-vIa6nRGTi9@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).