This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: RFC POSIX Fortran Interface
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: Jerry DeLisle <jvdelisle at verizon dot net>
- Cc: Fortran List <fortran at gcc dot gnu dot org>, Walter Spector <w6ws at earthlink dot net>
- Date: Sun, 14 Oct 2007 13:11:19 -0700
- Subject: Re: RFC POSIX Fortran Interface
- References: <471267C1.2000907@verizon.net>
On Sun, Oct 14, 2007 at 12:02:25PM -0700, Jerry DeLisle wrote:
>
> Attached is an initial start at implementing the POSIX fortran interface
> for gfortran.
>
> The attached implements the following:
>
> Subroutine: PXFCONST()
> Functions: IPXFCONST(), PXFISCONST(), PXFLENTRIM()
>
> I would like to extend my appreciation to Walter Spector for giving some
> initial guidance on this.
>
> The code is usable as is. My plan is to incorporate this into libgfortran
> for version 4.4 when the time comes.
>
Hi Jerry,
I haven't read through the code in detail; however, I'm wondering
what your plans are. In particular, do you plan to add the PXF
functions as gfortran intrinsic procedures? That is, are you
going to edit intrinsics.c to use the add_sym* routines, and
do the name mangling to add _gfortran_.
Personally, I'd rather have an independent libpxf (without the name
mangling) and a -fPXF or -fposix or some such option. Without -fPFX
the libraries during link would remain as is. With -fPFX, the
gfortran frontend would then add -lpxf before the -lgfortran linker
option. This would allow someone (perhaps, Walt) to use their
own implementation of libpxf without worrying about whether gfortran
screws with the namespace.
It also appears that it may be appropriate to split all nonstandard
intrinsics out of libgfortran into libfunjunk, and simply treat these
as EXTERNAL references. This would reduce the whining about getarg
and iargc and ... Of course, this would then mean people would need
to use the -ffun-junk option.
--
Steve