I noticed that gfortran's coarray support did not link to the
http://www.opencoarrays.org/
As that library is needed to support parallelization, it makes sense to
have the link.
Motivated by someone claiming at ISC-HPC that GCC only supports a single
image.
And also motivated by Damian's presentation, which showed that
gfortran's coarrays could successfully run the ICAR atmospheric model
with 25,600 processes (OpenCoarrays with OpenSHMEM backend), which
definitely is more than one image :-)
I think mentioning the existing libcaf_single is still useful, even
though it is only of limited use (except that it does ship with GCC and
permits to do some testings. Especially, it is used by GCC's testsuite).
OK for mainline?
Tobias
Fortran: invoke.texi - link to OpenCoarrays.org + mention libcaf_single
gcc/fortran/ChangeLog:
* invoke.texi (fcoarray): Link to OpenCoarrays.org;
mention libcaf_single.
gcc/fortran/invoke.texi | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/gcc/fortran/invoke.texi b/gcc/fortran/invoke.texi
index 40e8e4a7cdd..78a2910b8d8 100644
--- a/gcc/fortran/invoke.texi
+++ b/gcc/fortran/invoke.texi
@@ -1753,7 +1753,10 @@ Single-image mode, i.e. @code{num_images()} is always one.
@item @samp{lib}
Library-based coarray parallelization; a suitable GNU Fortran coarray
-library needs to be linked.
+library needs to be linked such as @url{http://opencoarrays.org}.
+Alternatively, GCC's @code{libcaf_single} library can be linked,
+albeit it only supports a single image.
+
@end table
