From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: [committed] libgomp: Mark thread_limit clause to target construct as implemented
Date: Tue, 16 Nov 2021 10:25:54 +0100 [thread overview]
Message-ID: <20211116092554.GG2710@tucnak> (raw)
In-Reply-To: <8f14a3f6-0a5f-6c1e-a493-f4b9ce3c4ebb@codesourcery.com>
On Mon, Nov 15, 2021 at 02:00:42PM +0100, Tobias Burnus wrote:
> Fortran: openmp: Add support for thread_limit clause on target
>
> gcc/fortran/ChangeLog:
>
> * openmp.c (OMP_TARGET_CLAUSES): Add thread_limit.
> * trans-openmp.c (gfc_split_omp_clauses): Add thread_limit also to
> teams.
After the Fortran changes we can mark it as implemented...
Bootstrapped/regtested on x86_64-linux and i686-linux, committed to trunk.
2021-11-16 Jakub Jelinek <jakub@redhat.com>
* libgomp.texi (OpenMP 5.1): Mark thread_limit clause to target
construct as implemented.
--- libgomp/libgomp.texi.jj 2021-10-27 09:24:43.312822017 +0200
+++ libgomp/libgomp.texi 2021-11-15 22:29:35.210487522 +0100
@@ -292,7 +292,7 @@ The OpenMP 4.5 specification is fully su
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
Jakub
prev parent reply other threads:[~2021-11-16 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 12:05 [PATCH] openmp: Add support for thread_limit clause on target Jakub Jelinek
2021-11-15 13:00 ` Tobias Burnus
2021-11-15 13:01 ` Jakub Jelinek
2021-11-16 9:25 ` Jakub Jelinek [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=20211116092554.GG2710@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).