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 r13-5287] libgomp.texi: Impl. status - non-rect loop nest only partial
Date: Mon, 23 Jan 2023 08:42:48 +0000 (GMT)	[thread overview]
Message-ID: <20230123084248.354203858D38@sourceware.org> (raw)

https://gcc.gnu.org/g:20552407ae11b61fccb46b3e96a8814e790254e7

commit r13-5287-g20552407ae11b61fccb46b3e96a8814e790254e7
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Mon Jan 23 09:40:41 2023 +0100

    libgomp.texi: Impl. status - non-rect loop nest only partial
    
    libgomp/
            * libgomp.texi (OpenMP 5.0): Set non-rectangular
            loop nest back to 'P' as Fortran support is incomplete.

Diff:
---
 libgomp/libgomp.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libgomp/libgomp.texi b/libgomp/libgomp.texi
index 1267c2304a5..67a05111289 100644
--- a/libgomp/libgomp.texi
+++ b/libgomp/libgomp.texi
@@ -195,7 +195,7 @@ The OpenMP 4.5 specification is fully supported.
       @tab complete but no non-host devices provides @code{unified_address},
       @code{unified_shared_memory} or @code{reverse_offload}
 @item @code{teams} construct outside an enclosing target region @tab Y @tab
-@item Non-rectangular loop nests @tab Y @tab
+@item Non-rectangular loop nests @tab P @tab Full support for C/C++, partial for Fortran
 @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

                 reply	other threads:[~2023-01-23  8:42 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=20230123084248.354203858D38@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: 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).