From: Sandra Loosemore <sandra@codesourcery.com>
To: <gcc-patches@gcc.gnu.org>
Cc: <jakub@redhat.com>, <tobias@codesourcery.com>
Subject: [COMMITTED V3 6/6] OpenMP: Document support for imperfectly-nested loops.
Date: Fri, 25 Aug 2023 13:47:14 -0600 [thread overview]
Message-ID: <20230825194714.627157-7-sandra@codesourcery.com> (raw)
In-Reply-To: <20230825194714.627157-1-sandra@codesourcery.com>
libgomp/ChangeLog
* libgomp.texi (OpenMP 5.0): Imperfectly-nested loops are done.
---
libgomp/libgomp.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libgomp/libgomp.texi b/libgomp/libgomp.texi
index 5c91163893f..4aad8cc52f4 100644
--- a/libgomp/libgomp.texi
+++ b/libgomp/libgomp.texi
@@ -200,7 +200,7 @@ The OpenMP 4.5 specification is fully supported.
@item @code{!=} as relational-op in canonical loop form for C/C++ @tab Y @tab
@item @code{nonmonotonic} as default loop schedule modifier for worksharing-loop
constructs @tab Y @tab
-@item Collapse of associated loops that are imperfectly nested loops @tab N @tab
+@item Collapse of associated loops that are imperfectly nested loops @tab Y @tab
@item Clauses @code{if}, @code{nontemporal} and @code{order(concurrent)} in
@code{simd} construct @tab Y @tab
@item @code{atomic} constructs in @code{simd} @tab Y @tab
--
2.31.1
prev parent reply other threads:[~2023-08-25 19:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 19:47 [COMMITTED V3 0/6] Support " Sandra Loosemore
2023-08-25 19:47 ` [COMMITTED V3 1/6] OpenMP: Add OMP_STRUCTURED_BLOCK and GIMPLE_OMP_STRUCTURED_BLOCK Sandra Loosemore
2023-08-25 19:47 ` [COMMITTED V3 2/6] OpenMP: C front end support for imperfectly-nested loops Sandra Loosemore
2023-08-25 19:47 ` [COMMITTED V3 3/6] OpenMP: C++ " Sandra Loosemore
2023-08-25 19:47 ` [COMMITTED V3 4/6] OpenMP: New C/C++ testcases for imperfectly nested loops Sandra Loosemore
2023-08-25 19:47 ` [COMMITTED V3 5/6] OpenMP: Fortran support for imperfectly-nested loops Sandra Loosemore
2023-08-25 19:47 ` Sandra Loosemore [this message]
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=20230825194714.627157-7-sandra@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--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).