From: Tobias Burnus <tobias@codesourcery.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>
Subject: [Patch] OpenMP: Add omp_in_explicit_task to omp_runtime_api_call
Date: Wed, 15 Mar 2023 15:24:04 +0100 [thread overview]
Message-ID: <6749cf41-bd73-4f6c-d565-67d2307164e4@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
When adding a new OpenMP routine, also omp_runtime_api_call needs
to be adapted - to get proper error like:
error: OpenMP runtime API call ‘omp_in_explicit_task’ in a region with ‘order(concurrent)’ clause
OK for mainline?
Tobias
PS: This routine was added in commit r13-3258-g0ec4e93fb9fa5e9d2424683c5fab1310c8ae2f76
PPS: I have not fully checked but I think it should be up to date; at least all
other recent additions include updates to that omp-low.cc function and at some point
I had checked it for completeness.
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
[-- Attachment #2: in-explicit.diff --]
[-- Type: text/x-patch, Size: 469 bytes --]
OpenMP: Add omp_in_explicit_task to omp_runtime_api_call
gcc/
* omp-low.cc (omp_runtime_api_call): Add omp_runtime_api_call.
diff --git a/gcc/omp-low.cc b/gcc/omp-low.cc
index 9757592c635..1818132830f 100644
--- a/gcc/omp-low.cc
+++ b/gcc/omp-low.cc
@@ -4082,6 +4082,7 @@ omp_runtime_api_call (const_tree fndecl)
"get_thread_num",
"get_wtick",
"get_wtime",
+ "in_explicit_task",
"in_final",
"in_parallel",
"init_lock",
next reply other threads:[~2023-03-15 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 14:24 Tobias Burnus [this message]
2023-03-15 14:27 ` Jakub Jelinek
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=6749cf41-bd73-4f6c-d565-67d2307164e4@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).