Sandbox branch for gfortran 4.5 patches

[Paul Richard Thomas]

PS - The memory leak patch was actually FX's; I just added some extra
frills, including a working gfc_current_locus in trans*, and a bug
fix.

I can remove the extra options with no problem (FX, did you have
anything ready that used them?).  If it bootstraps and regtests OK,
should I commit?  After fixing the last round of bit-rot on this
patch, I do not want to have to do it again!

Cheers

Paul

On Tue, Jan 6, 2009 at 8:58 AM, Daniel Kraft <d@domob.eu> wrote:
> Steve Kargl wrote:
>>
>> On Mon, Jan 05, 2009 at 04:43:16PM -0800, Jerry DeLisle wrote:
>>>
>>> On IRC today Steve Kargl suggested that maybe we need a dedicated branch
>>> for 4.5 patches.
>>>
>>> This would allow us to commit patches and continue working with
>>> up-to-date svn status while we wait for 4.5 branch to happen, then we can
>>> merge back right after that. I know i have a number of patches backed up,
>>> waiting.
>>>
>>> This would allow us to get Janne's I/O patch, Daniels I/O patch, and my
>>> I/O patches put together as well a a few Front-end things I am aware of.
>>>
>>> If everyone concurs, who wants to set it up.  Maybe call it
>>> "gfortran-devel"
>
> I would agree with this idea.
>
>> Also, note there are Daniel's finalization patch, pault's memleak
>> option patch, my errmsg for [de]allocate patch, and ISTR a patch from
>> Janus for procedure pointers (but he may have already committed that).
>
> You may want to look at our patch tracker in the Wiki, I think it is
> supposed to list all pending 4.5 patches (not sure if it actually does),
> http://gcc.gnu.org/wiki/GFortranPatchTracker
>
> Cheers,
> Daniel
>
>
> --
> Done:  Arc-Bar-Cav-Rog-Sam-Tou-Val-Wiz
> To go: Hea-Kni-Mon-Pri-Ran
>



-- 
The knack of flying is learning how to throw yourself at the ground and miss.
       --Hitchhikers Guide to the Galaxy