[Bug ipa/97346] IPA reference reference_vars_to_consider leaks

2021-02-14 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97346 Richard Biener changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug ipa/97346] IPA reference reference_vars_to_consider leaks

2021-02-14 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97346 --- Comment #9 from CVS Commits --- The master branch has been updated by Jan Hubicka : https://gcc.gnu.org/g:9966699d7a9d8e35c0c4cf9a945bcf90ef874f2d commit r11-7240-g9966699d7a9d8e35c0c4cf9a945bcf90ef874f2d Author: Jan Hubicka Date: Sun

[Bug ipa/97346] IPA reference reference_vars_to_consider leaks

2021-02-10 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97346 --- Comment #8 from Richard Biener --- (In reply to Jan Hubicka from comment #7) > I tested yesterday this one (which makes the lifetime bit more explicit > - during propagation it is for dumps only). Sorry for not posting it > earlier. I just

[Bug ipa/97346] IPA reference reference_vars_to_consider leaks

2021-02-10 Thread hubicka at ucw dot cz via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97346 --- Comment #7 from Jan Hubicka --- I tested yesterday this one (which makes the lifetime bit more explicit - during propagation it is for dumps only). Sorry for not posting it earlier. I just wanted to double check tha tleak is gone. diff

[Bug ipa/97346] IPA reference reference_vars_to_consider leaks

2021-02-10 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97346 --- Comment #6 from Richard Biener --- I'm testing the following which fixes the leak(s) diff --git a/gcc/ipa-reference.c b/gcc/ipa-reference.c index 2ea2a6d5327..a6b79fb9381 100644 --- a/gcc/ipa-reference.c +++ b/gcc/ipa-reference.c @@ -966,8

[Bug ipa/97346] IPA reference reference_vars_to_consider leaks

2021-02-10 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97346 --- Comment #5 from Richard Biener --- (In reply to Richard Biener from comment #4) > So like the following? Note the leak is the allcoation from ipa_init > being not released when we do the vec_alloc in >

[Bug ipa/97346] IPA reference reference_vars_to_consider leaks

2021-02-10 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97346 --- Comment #4 from Richard Biener --- So like the following? Note the leak is the allcoation from ipa_init being not released when we do the vec_alloc in ipa_reference_write_optimization_summary (maybe this function wants to use its own

[Bug ipa/97346] IPA reference reference_vars_to_consider leaks

2021-02-08 Thread hubicka at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97346 Jan Hubicka changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug ipa/97346] IPA reference reference_vars_to_consider leaks

2021-02-08 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97346 --- Comment #2 from Richard Biener --- Ping. This is annoying and pops up with each and every valgrind --leak-check=full ...

[Bug ipa/97346] IPA reference reference_vars_to_consider leaks

2020-10-09 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97346 --- Comment #1 from Richard Biener --- At least diff --git a/gcc/ipa-reference.c b/gcc/ipa-reference.c index 4a6c011c525..6df4be09471 100644 --- a/gcc/ipa-reference.c +++ b/gcc/ipa-reference.c @@ -1114,7 +1113,8 @@