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 r12-5296] libgomp: Mark thread_limit clause to target construct as implemented
Date: Tue, 16 Nov 2021 09:22:50 +0000 (GMT)	[thread overview]
Message-ID: <20211116092250.35E033858414@sourceware.org> (raw)

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

commit r12-5296-g9ceaf0fee35f6c79cda60e35aad27598dd4dcee6
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue Nov 16 10:21:56 2021 +0100

    libgomp: Mark thread_limit clause to target construct as implemented
    
    After the Fortran changes we can mark it as implemented...
    
    2021-11-16  Jakub Jelinek  <jakub@redhat.com>
    
            * libgomp.texi (OpenMP 5.1): Mark thread_limit clause to target
            construct as implemented.

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

diff --git a/libgomp/libgomp.texi b/libgomp/libgomp.texi
index fd747b91192..299960921f8 100644
--- a/libgomp/libgomp.texi
+++ b/libgomp/libgomp.texi
@@ -292,7 +292,7 @@ The OpenMP 4.5 specification is fully supported.
       clauses of the taskloop construct @tab Y @tab
 @item @code{align} clause/modifier in @code{allocate} directive/clause
       and @code{allocator} directive @tab P @tab C/C++ on clause only
-@item @code{thread_limit} clause to @code{target} construct @tab N @tab
+@item @code{thread_limit} clause to @code{target} construct @tab Y @tab
 @item @code{has_device_addr} clause to @code{target} construct @tab N @tab
 @item iterators in @code{target update} motion clauses and @code{map}
       clauses @tab N @tab


                 reply	other threads:[~2021-11-16  9:22 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=20211116092250.35E033858414@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).