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 r13-562] libgomp: Clarify that omp_display_env is fully implemented
Date: Tue, 17 May 2022 15:01:05 +0000 (GMT)	[thread overview]
Message-ID: <20220517150105.6F69E3858D3C@sourceware.org> (raw)

https://gcc.gnu.org/g:741478ed3ed51658af476bccbc198da931e41d44

commit r13-562-g741478ed3ed51658af476bccbc198da931e41d44
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue May 17 16:58:26 2022 +0200

    libgomp: Clarify that omp_display_env is fully implemented
    
    OpenMP 5.2 added
    "When called from within a target region the effect is unspecified."
    restriction to omp_display_env, so it is ok not to support it in
    target regions (worst case we could add an empty implementation
    or one with __builtin_trap in there).
    
    2022-05-17  Jakub Jelinek  <jakub@redhat.com>
    
            * libgomp.texi (OpenMP 5.1): Remove "Not inside target regions"
            comment for omp_display_env feature.

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

diff --git a/libgomp/libgomp.texi b/libgomp/libgomp.texi
index 629ad2f5084..9f40bae1247 100644
--- a/libgomp/libgomp.texi
+++ b/libgomp/libgomp.texi
@@ -321,8 +321,7 @@ The OpenMP 4.5 specification is fully supported.
       @code{omp_aligned_calloc} runtime routines @tab Y @tab
 @item @code{omp_alloctrait_key_t} enum: @code{omp_atv_serialized} added,
       @code{omp_atv_default} changed @tab Y @tab
-@item @code{omp_display_env} runtime routine @tab Y
-      @tab Not inside @code{target} regions
+@item @code{omp_display_env} runtime routine @tab Y @tab
 @item @code{ompt_scope_endpoint_t} enum: @code{ompt_scope_beginend} @tab N @tab
 @item @code{ompt_sync_region_t} enum additions @tab N @tab
 @item @code{ompt_state_t} enum: @code{ompt_state_wait_barrier_implementation}


                 reply	other threads:[~2022-05-17 15:01 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=20220517150105.6F69E3858D3C@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).