This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Patch, Fortran, 4.7] PR 18918 - Add initial support for a coarray communication library
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: Tobias Burnus <burnus at net-b dot de>
- Cc: gcc patches <gcc-patches at gcc dot gnu dot org>, gfortran <fortran at gcc dot gnu dot org>
- Date: Sat, 19 Mar 2011 10:26:07 -0700
- Subject: Re: [Patch, Fortran, 4.7] PR 18918 - Add initial support for a coarray communication library
- References: <4D84D875.9010501@net-b.de>
On Sat, Mar 19, 2011 at 05:23:17PM +0100, Tobias Burnus wrote:
>
> My idea is to place those library into libgfortran/caf. The user has to
> compile them themselves and link it then to their "gfortran
> -fcoarray=lib" compiled program. (Cf.
> http://gcc.gnu.org/ml/fortran/2011-03/msg00003.html).
See below at [1].
> Build and regtested on x86-64-linux.
> (a) Is the patch OK for the 4.7 trunk?
> (b) Are the libgfortrancaf.h, libgfortrancaf_mpi.c and
> libgfortrancaf_single.c OK for inclusion at libgfortran/caf?
>
Just a comment on names. Since you are planning to install
these in libgfortran/caf, please shorten the file names to
caf.h, caf_mpi.c, and caf_single.c. Consider this a friendly
RSI prevention measure.
[1] I don't understand what you mean by the above. Are you saying that
gcc would install caf.h, caf_mpi.c, etc in say
lib/gcc/i386-unknown-freebsd9.0/4.7.0/libgfortran
and a user would need to do
gfortran -fcoarray=mpi file.f90 ${PATH}/lib/gcc/i386-unknown-freebsd9.0/4.7.0/libgfortran/caf_mpi.c
to compile her code to use coarrays?
--
Steve