https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113476
--- Comment #14 from Jakub Jelinek ---
Ah, ok, in that case it can wait for stage1.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113476
--- Comment #13 from Aldy Hernandez ---
(In reply to Jakub Jelinek from comment #12)
> (In reply to Aldy Hernandez from comment #11)
> > Both patches pass test. Up to the release maintainers to decide if they
> > want to include them in this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113476
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113476
--- Comment #11 from Aldy Hernandez ---
Both patches pass test. Up to the release maintainers to decide if they want
to include them in this release. Otherwise, I'll queue them up for later.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113476
--- Comment #10 from Aldy Hernandez ---
Created attachment 57478
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57478=edit
Remove GTY support for vrange and friends
Bootstraps. Tests are pending.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113476
--- Comment #9 from Aldy Hernandez ---
Created attachment 57477
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57477=edit
Remove virtual from int_range destructor.
Bootstraps. Tests are pending.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113476
--- Comment #8 from Aldy Hernandez ---
(In reply to Richard Biener from comment #5)
> (In reply to Martin Jambor from comment #4)
> > The right place where to free stuff in lattices post-IPA would be in
> > ipa_node_params::~ipa_node_params()
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113476
--- Comment #7 from Aldy Hernandez ---
Let me see if I can untangle things here. Thanks for chasing
this down, BTW.
Value_Range doesn't need a CTOR because it has an int_range_max which
does have one (courtesy of int_range<>), so things get
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113476
--- Comment #6 from Martin Jambor ---
I have proposed a patch on the mailing list that converts the array of lattices
to a vector:
https://inbox.sourceware.org/gcc-patches/ri6frxoxzpk@virgil.suse.cz/T/#u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113476
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2024-01-23
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113476
--- Comment #4 from Martin Jambor ---
The right place where to free stuff in lattices post-IPA would be in
ipa_node_params::~ipa_node_params() where we should iterate over lattices and
deinitialize them or perhaps destruct the array because
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113476
Richard Biener changed:
What|Removed |Added
CC||aldyh at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113476
--- Comment #2 from Richard Biener ---
In fact it occurs elsewhere as well:
==1854== 81,616 bytes in 2 blocks are possibly lost in loss record 1,363 of
1,373
==1854==at 0x505A1DF: operator new[](unsigned long) (in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113476
--- Comment #1 from Richard Biener ---
Created attachment 57138
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57138=edit
testcase
For convenience here it is. I checked
valgrind --leak-check=full ./cc1 -quiet -O3 -march=znver4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113476
Richard Biener changed:
What|Removed |Added
CC||amacleod at redhat dot com
Target
15 matches
Mail list logo
