This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/80477] [OOP] Polymorphic function result generates memory leak


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80477

--- Comment #7 from janus at gcc dot gnu.org ---
(In reply to Stefano Zaghi from comment #6)
> As I tried to clarify to Steve, mine was absolutely not a polemic question:

No offense taken. Asking questions is not a crime ;)


> What I meant was "because the bug is known from 2014, can I conclude that
> there are not any developer who takes care (for time/interest lacking) about
> this in a reasonable time?". It is just a hint-request about a roadmap

I'm sorry to disappoint you, but there simply is no roadmap and I'm not able to
provide one. That's just not how things work with gfortran.

If you absolutely critically depend on some feature being available in a
certain time-frame, then your best options are probably:
a) Try to implement it yourself or
b) pay someone to implement it.



> My concern was that the bug was
> very difficult to solve and you are too few to solve it.

I don't think the bug is incredibly difficult to solve. I already have a basic
understanding of what's missing (see my analysis above) and I might look into
fixing it soon. BUT: I simply can not give you any roadmaps or guarantees for
that.

And yes, gfortran could definitely use some more manpower. If you are willing
to help (or know someone who is), you're certainly welcome.


> I am going to create a detailed report (within a github repository) taking
> into account many combinations: it seems that if I add an allocatable
> component alongside the static one, the leaks disappear (although this does
> not happen in a real,omplex code where both static and dynamic components
> are present). If it is of some help, I would like to share with you.

Sure, that will probably help to understand the problem. Thanks for your
efforts.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]