Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: brichardson at structint dot com
Target Milestone: ---
It appears that without an intermediate value to save the result of the
function call, the value returned by the function ends up being
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: brichardson at structint dot com
Target Milestone: ---
It appears that, if a function returns a polymorphic (i.e. class(thing))
variable, if the result is not assigned to a variable
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: brichardson at structint dot com
Target Milestone: ---
It appears that trying to do polymorphic dispatch to a function that has a
polymorphic return type leads to a memory leak. But, by
: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: brichardson at structint dot com
Target Milestone: ---
Allocate on assignment for polymorphic scalars causes a memory leak. The
following program and execution demonstrates the problem.
program assignment_memory_leak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90069
--- Comment #2 from Brad Richardson ---
(In reply to Dominique d'Humieres from comment #1)
> Confirmed from at least 4.8 up to trunk (9.0). Why is it not a duplicate of
> pr90072?
Because pr90072 occurs even with an intermediate variable.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85042
Brad Richardson changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
Assignee: unassigned at gcc dot gnu.org
Reporter: brichardson at structint dot com
Target Milestone: ---
Given an empty, abstract derived type, and an empty derived type which extends
from it, trying to assign to an allocatable variable of the abstract class
causes the compiler to
