[Bug fortran/69080] No automatic deallocation of allocatable function results

2016-09-30 Thread sv.muel...@tu-braunschweig.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69080 --- Comment #16 from Mueller --- I stumbled upon this problem when creating an object-oriented string class if I remember correctly. Some procedure would allocate a string and return it (like dummy_create_allocatable in the test prog). The callin

[Bug fortran/69080] No automatic deallocation of allocatable function results

2016-09-28 Thread sv.muel...@tu-braunschweig.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69080 --- Comment #14 from Mueller --- I'd really like to know why this report has been closed although there may be a problem with deallocation. I think the rephrasing of Mikael pinpointed what I meant.

[Bug fortran/69080] No automatic deallocation of allocatable function results

2016-01-06 Thread sv.muel...@tu-braunschweig.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69080 --- Comment #9 from Mueller --- (In reply to Mueller from comment #8) > I think, in theory, the compiler could detect something like > > call some_subroutine(function_returning_allocatable()) > > to be a potential case for automatic deallocatio

[Bug fortran/69080] No automatic deallocation of allocatable function results

2016-01-06 Thread sv.muel...@tu-braunschweig.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69080 --- Comment #8 from Mueller --- (In reply to Dominique d'Humieres from comment #6) > > I know that allocatables that are declared in the program itself aren't > > deallocated automatically because of the implicit save attribute. > > But my think

[Bug fortran/69080] No automatic deallocation of allocatable function results

2016-01-06 Thread sv.muel...@tu-braunschweig.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69080 --- Comment #7 from sv.muel...@tu-braunschweig.de --- (In reply to kargl from comment #5) > When the execution of a procedure is terminated by execution of a > RETURN or END statement, an allocatable variable that is a named > local va

[Bug fortran/69080] No automatic deallocation of allocatable function results

2015-12-29 Thread sv.muel...@tu-braunschweig.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69080 --- Comment #4 from sv.muel...@tu-braunschweig.de --- Addendum to my last post: I refered to scalar allocatables, not arrays

[Bug fortran/69080] No automatic deallocation of allocatable function results

2015-12-29 Thread sv.muel...@tu-braunschweig.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69080 --- Comment #3 from sv.muel...@tu-braunschweig.de --- Thanks for testing this out! Indeed there aren't any leaks with your changes. Actually, leaving the module save statement uncommented produces the same positive result for me. Howev

[Bug fortran/69080] New: No automatic deallocation of allocatable function results

2015-12-29 Thread sv.muel...@tu-braunschweig.de
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: sv.muel...@tu-braunschweig.de Target Milestone: --- Created attachment 37186 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37186&action=edit Test program and module Note: Thi