From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 491913858C50; Fri, 10 Feb 2023 02:54:57 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 491913858C50
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1675997697;
	bh=+w/+tplN2gNbczK6HbNVay7eCkVQj4XuvnY69skTsL4=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Bl11lxMtabak7n0destcrvMjZXw0Kgr72LU64lcPuvZKXc7yt7I9mLv4AsWIjk75Q
	 wGp9Tluo5lGF+RV4Zy7r28exHvrjrCSrln32w0P2QWr5sIJV12BhPEdYNcRCKq7SAZ
	 VlLDmjp644eQPJgiFqvbWuMjcZy6Tao5VDUpG+24=
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108697] constructing a path-range-query is
 expensive
Date: Fri, 10 Feb 2023 02:54:56 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: compile-time-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amacleod at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108697-4-temvCsL5BJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108697-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108697-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

--- Comment #6 from Andrew Macleod <amacleod at redhat dot com> ---
(In reply to Aldy Hernandez from comment #5)
> (In reply to Richard Biener from comment #3)
> > 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?
>=20
> BTW, if putting the bitmap in the ssa_global_cache itself works, that's f=
ine
> as well, especially if it makes the ranger's cache faster :).

FYI, I have a prototype to do this... I'm just looking at whether it is bet=
ter
to integrate it in the class, or derive it from a performance point of view=
.=20
results soon.=