public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: Gerald Pfeifer <gerald@pfeifer.com>, Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [wwwdocs] gcc-13/changes.html + projects/gomp/: OpenMP update
Date: Sat, 21 Jan 2023 13:53:24 +0100	[thread overview]
Message-ID: <edbad229-57a4-22bf-a72f-989e1828e22f@codesourcery.com> (raw)
In-Reply-To: <5f59fa0a-f42d-8e83-0ea0-1f37d656acab@pfeifer.com>

On 21.01.23 13:48, Gerald Pfeifer wrote:
> Just one question: Does "all clauses are now accepted" refer to
>   - all (as in 100% of possible clauses), or
>   - <code>all</code> (as in a special kind of clause)?

The former – besides the listed 'unified_shared_memory',
'unified_address' and 'reverse_offload' clauses, there are
'dynamic_allocators' and 'atomic_default_mem_order' which are handled in
the compiler front end (by being ignored (always fulfilled) and by used
its argument as default value, respectively).

Thanks for the review. (I will commit/update the patch later.)

Tobias

-----------------
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

  reply	other threads:[~2023-01-21 12:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-02  7:37 Tobias Burnus
2022-09-08 15:40 ` Jakub Jelinek
2023-01-14 21:47 ` Gerald Pfeifer
2023-01-16  8:17   ` Tobias Burnus
2023-01-16 22:16     ` Gerald Pfeifer
2023-01-18 12:39       ` Tobias Burnus
2023-01-20 17:50         ` Jakub Jelinek
2023-01-21 12:48           ` Gerald Pfeifer
2023-01-21 12:53             ` Tobias Burnus [this message]
2023-01-23  9:00               ` Tobias Burnus
2023-01-23  9:06                 ` Gerald Pfeifer

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=edbad229-57a4-22bf-a72f-989e1828e22f@codesourcery.com \
    --to=tobias@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --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).