This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/65925] Memory leak with source allocation nested inside the source of another source allocation
- From: "damian at sourceryinstitute dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 08 May 2015 23:45:18 +0000
- Subject: [Bug fortran/65925] Memory leak with source allocation nested inside the source of another source allocation
- Auto-submitted: auto-generated
- References: <bug-65925-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65925
Damian Rouson <damian at sourceryinstitute dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Damian Rouson <damian at sourceryinstitute dot org> ---
This was a false alarm. Wrapping the following lines inside a bloc construct
eliminates the erroneous valgrind report.
class(base),allocatable :: d
allocate(d,source = newData())
Damian