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 #8 from Stefano Zaghi <stefano.zaghi at cnr dot it> ---
Dear Janus,

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

Good, thank you for the clarification.

> 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.

No disappointing at all: this is, indeed, the answer I was searching for taking
a decision. If there is not a "timeline" for this bug, because the option a) is
not up to me and option b) is currently impossible, this means that I have to
left GNU if I cannot find a workaround for the leaks quickly.

> 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 really would like to help, but I am not up to the task (I never go over
tutorial-level with C). Anyhow, if you can share your idea about the issue is
placed (files involved, rationale...) it could be a starting a point: I have a
colleague well-versed in C, maybe in some eons I could be of some help.

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

You are much more than welcome. After 25 April I'll provide my report.

My best regards.

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