public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-6076] libgomp: Fix comment typo
Date: Thu, 16 Feb 2023 11:14:01 +0000 (GMT)	[thread overview]
Message-ID: <20230216111401.D15383858D33@sourceware.org> (raw)

https://gcc.gnu.org/g:9d71955f383058f17362c1960bdf8ba2b8c74857

commit r13-6076-g9d71955f383058f17362c1960bdf8ba2b8c74857
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Thu Feb 16 12:10:19 2023 +0100

    libgomp: Fix comment typo
    
    I saw
    FAIL: libgomp.fortran/target-nowait-array-section.f90   -O  execution test
    in my last x86_64-linux bootstrap.  From quick skimming, it might be just
    unreliable test, which assumes that asynchronous execution wouldn't produce
    ordered sequence, but can't it happen even with asynchronous execution?
    
    That said, while skimming the test, I've noticed a comment typo and
    this patch fixes that up.
    
    2023-02-16  Jakub Jelinek  <jakub@redhat.com>
    
            * testsuite/libgomp.fortran/target-nowait-array-section.f90: Fix
            comment typo and improve its wording.

Diff:
---
 libgomp/testsuite/libgomp.fortran/target-nowait-array-section.f90 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libgomp/testsuite/libgomp.fortran/target-nowait-array-section.f90 b/libgomp/testsuite/libgomp.fortran/target-nowait-array-section.f90
index 3613b731676..783ad4f6ac1 100644
--- a/libgomp/testsuite/libgomp.fortran/target-nowait-array-section.f90
+++ b/libgomp/testsuite/libgomp.fortran/target-nowait-array-section.f90
@@ -1,4 +1,4 @@
-! Runs the the target region asynchrolously and checks for it
+! Run the target region asynchronously and check it
 !
 ! Note that  map(alloc: work(:, i)) + nowait  should be safe
 ! given that a nondescriptor array is used. However, it still

                 reply	other threads:[~2023-02-16 11:14 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=20230216111401.D15383858D33@sourceware.org \
    --to=jakub@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: 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).