[Bug fortran/38319] Memory leaks in allocatable component expressions

2021-02-01 Thread pault at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38319 --- Comment #12 from Paul Thomas --- (In reply to Tobias Burnus from comment #11) > Related / same issue: > https://gcc.gnu.org/pipermail/fortran/2021-January/055654.html Hi Tobias, Over the weekend, I had a stab at fixing this recent issue. I

[Bug fortran/38319] Memory leaks in allocatable component expressions

2021-02-01 Thread burnus at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38319 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org --- Comment

[Bug fortran/38319] Memory leaks in allocatable component expressions

2018-03-04 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38319 Dominique d'Humieres changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug fortran/38319] Memory leaks in allocatable component expressions

2016-11-25 Thread pault at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38319 --- Comment #10 from Paul Thomas --- Of the testcases originally highlighted: alloc_comp_assign_2.f90 still leaks alloc_comp_assign_4.f90 still leaks alloc_comp_basics_2.f90 still leaks alloc_comp_basics_5.f90 is OK -

[Bug fortran/38319] Memory leaks in allocatable component expressions

2016-11-22 Thread pault at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38319 --- Comment #9 from Paul Thomas --- class_array_15.f03 leaks from line 65-66: allocate (indv(2), source = [individual(1, [99,999]), & individual(2, [999,])]) ==22496== HEAP SUMMARY: ==22496== in use at

[Bug fortran/38319] Memory leaks in allocatable component expressions

2015-01-03 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38319 --- Comment #8 from janus at gcc dot gnu.org --- (In reply to Paul Thomas from comment #0) alloc_comp_assign_4.f90 nested constructors(line 56) With current trunk I see additional leaks in lines 28 and 29. Those are again due to not

[Bug fortran/38319] Memory leaks in allocatable component expressions

2015-01-03 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38319 janus at gcc dot gnu.org changed: What|Removed |Added CC||janus at gcc dot gnu.org ---

[Bug fortran/38319] Memory leaks in allocatable component expressions

2012-02-22 Thread xiaoyuanbo at yeah dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38319 xiaoyuanbo xiaoyuanbo at yeah dot net changed: What|Removed |Added CC||xiaoyuanbo at yeah

[Bug fortran/38319] Memory leaks in allocatable component expressions

2010-02-25 Thread paul dot richard dot thomas at gmail dot com
--- Comment #4 from paul dot richard dot thomas at gmail dot com 2010-02-25 12:50 --- Subject: Re: Memory leaks in allocatable component expressions --- Comment #3 from burnus at gcc dot gnu dot org  2010-02-25 07:38 --- Paul, can you try with  valgrind

[Bug fortran/38319] Memory leaks in allocatable component expressions

2010-02-25 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2010-02-25 13:54 --- type :: thytype integer(4), allocatable :: h(:) end type thytype type :: mytype type(thytype), allocatable :: q(:) end type mytype type (mytype) :: x x = mytype ([thytype([555])]) end Reduced

[Bug fortran/38319] Memory leaks in allocatable component expressions

2010-02-24 Thread pault at gcc dot gnu dot org
--- Comment #2 from pault at gcc dot gnu dot org 2010-02-24 20:31 --- I have been having trouble in recent times detecting these memory leaks. Neither FC9 nor RHEL5.2 x86_64 seem to show them with valgrind. Since I know that others still see them, I wonder are there any ideas what I

[Bug fortran/38319] Memory leaks in allocatable component expressions

2010-02-24 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2010-02-25 07:38 --- Paul, can you try with valgrind --leak-check=full ? Without the =full option, I also do not get any line info output but just in the summary definitely lost: 288 bytes in 4 blocks. --

[Bug fortran/38319] Memory leaks in allocatable component expressions

2009-07-30 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2009-07-30 19:07 --- See also http://gcc.gnu.org/ml/fortran/2009-07/msg00260.html and PR 40899. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38319

[Bug fortran/38319] Memory leaks in allocatable component expressions

2008-11-29 Thread pault at gcc dot gnu dot org
-- pault at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last