https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94109
Thomas Koenig changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #13 from Thomas Koenig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94109
--- Comment #12 from Antony Lewis ---
Valgrid report is
HEAP SUMMARY:
==23446== in use at exit: 40,000 bytes in 1 blocks
==23446== total heap usage: 26 allocs, 25 frees, 93,657 bytes allocated
==23446==
==23446== 40,000 bytes in 1 blocks a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94109
--- Comment #11 from Antony Lewis ---
It took ages to narrow this down, but here's a simple test case that still
gives a leak with valgrind in gcc-8 HEAD, 8.4.0, 9.3.0 (OK with 7.4.0)
module debug
implicit none
Type Tester
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94109
--- Comment #10 from Thomas Koenig ---
(In reply to Dominique d'Humieres from comment #9)
> Is it a false positive or not?
You probably need a higher optimization level with -fanalyzer,
it doesn't show anything at -O. Nor does valgrind show an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94109
--- Comment #9 from Dominique d'Humieres ---
For the record:
% gfc pr94361.f90 -fanalyzer
pr94361.f90:24:0:
24 | end subroutine
|
Warning: leak of 'test.t.dat.data' [CWE-401] [-Wanalyzer-malloc-leak]
'leaker': events 1-11
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94109
--- Comment #8 from Thomas Koenig ---
Unfortunately, without a somewhat reduced test case, there is
not a lot I can do :-(
Could you run this under valgrind, pinpoint the memory
leaks (somewhat) and then try to reduce this?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94109
--- Comment #7 from Antony Lewis ---
However the reduced case of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94361
now seems to be OK.
However on trunk, the fix for 94361 seems to have introduced a leak that was
not there before: https://travis
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94109
--- Comment #6 from Antony Lewis ---
Thanks for looking in to it. I tried rebuilding my gcc8 docker and rerunning.
It now reports GNU Fortran (GCC) 8.4.1 20200602, however the leak still seems
to be there?
https://travis-ci.org/github/cmbant/CAM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94109
--- Comment #5 from Thomas Koenig ---
So, fixed with the patch for PR 94109?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94109
--- Comment #4 from Antony Lewis ---
Not sure why no one has at least picked up on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94361
since it is a reproducible regression with a simple test case, an a bug that
effectively kills some previousl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94109
--- Comment #3 from Antony Lewis ---
Although my reduced test in the other id case is one problem, it appears that
is not the only memory leak. Someone tested else on various gcc versions and
still found:
versionmemory leak
7.3.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94109
--- Comment #2 from Antony Lewis ---
This may be the test case, though I'm not 100% sure:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94361
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94109
Thomas Koenig changed:
What|Removed |Added
CC||tkoenig at gcc dot gnu.org
Last reconf
13 matches
Mail list logo
