This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/80477] [OOP] Polymorphic function result generates memory leak
- From: "stefano.zaghi at cnr dot it" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 26 Apr 2017 08:41:09 +0000
- Subject: [Bug fortran/80477] [OOP] Polymorphic function result generates memory leak
- Auto-submitted: auto-generated
- References: <bug-80477-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80477
--- Comment #13 from Stefano Zaghi <stefano.zaghi at cnr dot it> ---
Dear all,
I have done further test about Vipul's workaround, you can find my complete
report here
https://github.com/szaghi/leaks_hunter#results
Essentially, my current conclusion is that the workaround does not work always.
In particular the "simple inheritance leaker" test shows that the leak is still
generated no matter the workaround is used. In this last case, I think that
issues could be placed into the "child_t" finalizer: you can find the generated
code here
https://github.com/szaghi/leaks_hunter#note
I hope this can help for your patch.
My best regards.