public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sandra Loosemore <sloosemore@baylibre.com>
To: Tobias Burnus <tburnus@baylibre.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: [Patch] Fortran: invoke.texi - link to OpenCoarrays.org + mention libcaf_single
Date: Sun, 19 May 2024 18:31:27 -0600	[thread overview]
Message-ID: <fbbd75d1-eb45-4b96-825e-227132396ff5@baylibre.com> (raw)
In-Reply-To: <18e91ab2-7ddb-47d8-9383-d4c7689eecd9@baylibre.com>

On 5/19/24 02:01, Tobias Burnus wrote:
> I noticed that gfortran's coarray support did not link to the 
> http://www.opencoarrays.org/ >
> [snip]
> 
> 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}.

This would read better as

library such as @url{http://opencoarrays.org} needs to be linked.

> +Alternatively, GCC's @code{libcaf_single} library can be linked,
> +albeit it only supports a single image.
> +
>  @end table

OK with that tweak.

-Sandra




  parent reply	other threads:[~2024-05-20  0:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-19  8:01 Tobias Burnus
2024-05-19 10:24 ` FX Coudert
2024-05-20  0:31 ` Sandra Loosemore [this message]
2024-05-21  7:28   ` rep.dot.nop
2024-05-21  8:20     ` 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=fbbd75d1-eb45-4b96-825e-227132396ff5@baylibre.com \
    --to=sloosemore@baylibre.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tburnus@baylibre.com \
    /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).