This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Patch, Fortran] PR 48700: memory leak with MOVE_ALLOC
- From: Janus Weil <janus at gcc dot gnu dot org>
- To: Tobias Burnus <tobias dot burnus at physik dot fu-berlin dot de>
- Cc: gcc-patches at gcc dot gnu dot org, fortran at gcc dot gnu dot org
- Date: Wed, 18 May 2011 21:13:18 +0200
- Subject: Re: [Patch, Fortran] PR 48700: memory leak with MOVE_ALLOC
- References: <20110518150348.GA16586@physik.fu-berlin.de>
>> The patch was regtested on x86_64-unknown-linux-gnu. Ok for trunk?
>
> OK. Thanks for the patch!
Thanks, Tobias. Committed as r173874.
> (What next on your gfortran agenda?)
Well, I am pretty busy with my "day job" at university and working on
my PhD, which will not allow me to make huge leaps on gfortran anytime
soon (and was the reason for my abstinence from this mailing list
during the last weeks). However, I'll surely try to continue working
on a few PRs in the "OOP & friends" area. As the OOP wiki page shows,
there is enough work left to do in this respect (e.g. we urgently need
polymorphic deallocation and there are problems with type-bound
operators and assignments, just to name a few).
In case anyone feels a strong urge to implement polymorphic arrays or
finalization, please go ahead! I will probably not be able to take
this on myself in the next months, but I can offer some support and
advice regarding the present implementation of polymorphism and how to
extend it.
This is all I can promise right now ...
Cheers,
Janus
>> 2011-05-16 ?Janus Weil ?<janus@gcc.gnu.org>
>>
>> ? ? ? PR fortran/48700
>> ? ? ? * trans-intrinsic.c (gfc_conv_intrinsic_move_alloc): Deallocate 'TO'
>> ? ? ? argument to avoid memory leaks.
>>
>> 2011-05-16 ?Janus Weil ?<janus@gcc.gnu.org>
>>
>> ? ? ? PR fortran/48700
>> ? ? ? * gfortran.dg/move_alloc_4.f90: New.
>