This is the mail archive of the
mailing list for the GCC project.
Re: [Fwd: Re: [Patch, Fortran] PR fotran/35820 again: memory leak while resolving nested foralls.]
- From: Mikael Morin <mikael dot morin at tele2 dot fr>
- To: Tobias Burnus <burnus at net-b dot de>
- Cc: correctifs gcc <gcc-patches at gcc dot gnu dot org>, gfortran <fortran at gcc dot gnu dot org>
- Date: Wed, 05 Nov 2008 19:40:36 +0100
- Subject: Re: [Fwd: Re: [Patch, Fortran] PR fotran/35820 again: memory leak while resolving nested foralls.]
- References: <490AFEFB.email@example.com> <490B2763.firstname.lastname@example.org> <490B2A0F.email@example.com>
Tobias Burnus wrote:
> Mikael Morin wrote:
>> Mikael Morin wrote:
>>> I have not commit right yet, so feel free to commit for me.
>> I have commit access now, it was faster than expected, really. :)
>>> Otherwise, I can do it myself as soon as I'm allowed to (but I think we
>>> are a bit in a hurry, right?).
>> Committed as revision 141496.
> Question: Was this actually reviewed by someone? (Note that you have
> only a "Write After Approval" account.*)
> Glancing at it, it looked OK, but someone should re-check; I wouldn't
> count this as obvious ;-)
> (Yes, I know that we currently have a reviewing problem - lagging behind
> with several patches.)
> * actually, also so-called "MAINTAINERS" have to seek approval: "Note
> that individuals who maintain parts of the compiler as non-algorithmic
> maintainers need approval to check in algorithmic changes or changes
> outside of the parts of the compiler they maintain."
> For write after approval, see: http://gcc.gnu.org/svnwrite.html#policies
It's failing with version 4.3.2 too.
Should I backport ?