https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86567
Jason Merrill changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86567
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|8.3 |8.4
--- Comment #6 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86567
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86567
Jason Merrill changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86567
--- Comment #4 from Alexander Monakov ---
I think the problem is not exactly that maybe_constant_value keeps a lookup
cache, but rather that invoking maybe_constant_value may cause allocation of
uids. So it wouldn't be enough to simply avoid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86567
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|8.2 |8.3
--- Comment #3 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86567
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86567
Richard Biener changed:
What|Removed |Added
Version|unknown |8.1.1
Target Milestone|---
