From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Tobias Burnus <burnus@net-b.de>
Cc: gcc patches <gcc-patches@gcc.gnu.org>, gfortran <fortran@gcc.gnu.org>
Subject: Re: [Patch, Fortran, 4.7] PR 18918 - Add initial support for a coarray communication library
Date: Sat, 19 Mar 2011 17:26:00 -0000 [thread overview]
Message-ID: <20110319172607.GA3407@troutmask.apl.washington.edu> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2011-03-19 17:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 16:23 Tobias Burnus
2011-03-19 17:26 ` Steve Kargl [this message]
2011-03-19 18:01 ` Tobias Burnus
2011-03-19 19:25 ` Ralf Wildenhues
2011-03-19 21:09 ` Tobias Burnus
2011-03-24 15:54 ` *ping* " Tobias Burnus
2011-03-26 12:34 ` Tobias Burnus
2011-03-26 17:26 ` Jerry DeLisle
2011-03-27 13:03 ` Tobias Burnus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110319172607.GA3407@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).