This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
[Testsuite Fortran, Patch] Add coarray/ directory for coarray compile and run-time tests
- From: Tobias Burnus <burnus at net-b dot de>
- To: gcc patches <gcc-patches at gcc dot gnu dot org>, gfortran <fortran at gcc dot gnu dot org>, Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>, Mike Stump <mikestump at comcast dot net>, Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>
- Date: Sat, 30 Apr 2011 20:55:53 +0200
- Subject: [Testsuite Fortran, Patch] Add coarray/ directory for coarray compile and run-time tests
The patch adds the directory
gcc/testsuite/gfortran.dg/coarray/
All files in this directory are compiled/linked/run with
"-fcoarray=single" and "-fcoarray=lib -lcaf_single". The compilation is
only done with -O2 - instead of cycling through all optimization
options; however, one could change that.
The coarray_16.f90 "dg-do run" test is -fcoarray=lib proof and can be
moved into that directory.
Questions:
a) Is run-time testing with -O2 sufficient - or should all
DG_TORTURE_OPTIONS be used?
b) Is the way of adding "-lcaf_single" acceptable?
c) What's the best way to add support for -lcaf_mpi? I think, the user
needs to specify both compile/link options, e.g.
GCC_CAF_FLAGS="`mpif90 -showme` -lcaf_mpi"
or
GCC_CAF_FFLAGS=`mpif90 -showme:compile`
GCC_CAF_LDFLAGS="`mpif90 -showme:link` -lcaf_mpi"
and a run command, e.g.
GCC_CAF_RUN="mpiexec -n 2"
either directly or via site.exp - which defaults to unset.
Is the patch OK for the trunk?
Tobias