public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-1002] fortran/intrinsic.texi: Use proper variable name Date: Sun, 23 May 2021 09:58:29 +0000 (GMT) [thread overview] Message-ID: <20210523095829.0BB703857C52@sourceware.org> (raw) https://gcc.gnu.org/g:5d3ef9189a7c57679b5fb06e51c90479df0548b0 commit r12-1002-g5d3ef9189a7c57679b5fb06e51c90479df0548b0 Author: Tobias Burnus <tobias@codesourcery.com> Date: Sun May 23 11:56:39 2021 +0200 fortran/intrinsic.texi: Use proper variable name gcc/fortran/ChangeLog: * intrinsic.texi (ATOMIC_ADD, ATOMIC_FETCH_ADD): Use the proper variable name in the description. Diff: --- gcc/fortran/intrinsic.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/fortran/intrinsic.texi b/gcc/fortran/intrinsic.texi index a62508745fd..ad164137986 100644 --- a/gcc/fortran/intrinsic.texi +++ b/gcc/fortran/intrinsic.texi @@ -1870,7 +1870,7 @@ Inverse function: @gol @table @asis @item @emph{Description}: -@code{ATOMIC_ADD(ATOM, VALUE)} atomically adds the value of @var{VAR} to the +@code{ATOMIC_ADD(ATOM, VALUE)} atomically adds the value of @var{VALUE} to the variable @var{ATOM}. When @var{STAT} is present and the invocation was successful, it is assigned the value 0. If it is present and the invocation has failed, it is assigned a positive value; in particular, for a coindexed @@ -2090,7 +2090,7 @@ end program atomic @table @asis @item @emph{Description}: @code{ATOMIC_FETCH_ADD(ATOM, VALUE, OLD)} atomically stores the value of -@var{ATOM} in @var{OLD} and adds the value of @var{VAR} to the +@var{ATOM} in @var{OLD} and adds the value of @var{VALUE} to the variable @var{ATOM}. When @var{STAT} is present and the invocation was successful, it is assigned the value 0. If it is present and the invocation has failed, it is assigned a positive value; in particular, for a coindexed
reply other threads:[~2021-05-23 9:58 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210523095829.0BB703857C52@sourceware.org \ --to=burnus@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).