From: Jakub Jelinek <jakub@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: Tobias Burnus <tobias@codesourcery.com>
Subject: [committed] libgomp: Fix comment typo
Date: Thu, 16 Feb 2023 12:20:17 +0100 [thread overview]
Message-ID: <Y+4RZHrFT1+jua/0@tucnak> (raw)
Hi!
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.
Tested on x86_64-linux, committed to trunk.
2023-02-16 Jakub Jelinek <jakub@redhat.com>
* testsuite/libgomp.fortran/target-nowait-array-section.f90: Fix
comment typo and improve its wording.
--- libgomp/testsuite/libgomp.fortran/target-nowait-array-section.f90.jj 2022-05-16 09:46:02.329060126 +0200
+++ libgomp/testsuite/libgomp.fortran/target-nowait-array-section.f90 2023-02-16 12:04:11.227347228 +0100
@@ -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
Jakub
next prev reply other threads:[~2023-02-16 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 17:21 [Patch] OpenMP/Fortran: Use firstprivat not alloc for ptr attach for arrays Tobias Burnus
2022-05-13 17:44 ` Jakub Jelinek
2022-11-12 9:19 ` Thomas Schwinge
2023-02-16 11:20 ` Jakub Jelinek [this message]
2023-02-16 14:50 ` 'libgomp.fortran/target-nowait-array-section.f90' (was: [committed] libgomp: Fix comment typo) Thomas Schwinge
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=Y+4RZHrFT1+jua/0@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=tobias@codesourcery.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).