From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch] OpenMP: Add omp_in_explicit_task to omp_runtime_api_call
Date: Wed, 15 Mar 2023 15:27:24 +0100 [thread overview]
Message-ID: <ZBHVzILdnOjcNKJJ@tucnak> (raw)
In-Reply-To: <6749cf41-bd73-4f6c-d565-67d2307164e4@codesourcery.com>
On Wed, Mar 15, 2023 at 03:24:04PM +0100, Tobias Burnus wrote:
> 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?
Yes, thanks.
> 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",
Jakub
prev parent reply other threads:[~2023-03-15 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 14:24 Tobias Burnus
2023-03-15 14:27 ` 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=ZBHVzILdnOjcNKJJ@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).