[gfortran,patch] We don't need libgfortran wrappers for malloc and free

Steve Kargl sgk@troutmask.apl.washington.edu
Mon May 7 17:54:00 GMT 2007


On Mon, May 07, 2007 at 04:47:12PM +0200, Fran?ois-Xavier Coudert wrote:
> 
> This patch is not a regression, wrong-code or ice-on-valid-code fix,
> but I've had it ready for submission for 3 months, so I decided to
> submit it. It fixes PR30723, a missed-optimization issue with the way
> we allocate memory for internal use.
> 
>        PR fortran/30723
>        * runtime/memory.c (internal_malloc, internal_malloc64,
>        internal_free): Remove.
>        * runtime/error.c (os_error): Export function.
>        * intrinsics/move_alloc.c: Include stdlib.h.
>        (move_alloc): Call free instead of internal_free.
>        (move_alloc_c): Wrap long lines.
>        * libgfortran.h (os_error): Export prototype.
>        (internal_free): Remove prototype.
>        * gfortran.map (GFORTRAN_1.0): Remove _gfortran_internal_free,
>        _gfortran_internal_malloc and _gfortran_internal_malloc64.
>        Add _gfortran_os_error.

What potential impact will this have on the ISO C Binding patch
that I'm trying to pull out of the fortran-experiments branch?

-- 
Steve



More information about the Fortran mailing list