This is the mail archive of the gcc-patches@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]

Re: [Fwd: Re: [Patch, Fortran] PR fotran/35820 again: memory leak while resolving nested foralls.]


Tobias Burnus wrote:
> Hi,
> 
> 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.)
> 
> Tobias
> 
> * 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 ?

Mikael


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