public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/omp/gcc-12] libgomp: Clarify that omp_display_env is fully implemented
Date: Thu,  8 Sep 2022 12:25:24 +0000 (GMT)	[thread overview]
Message-ID: <20220908122524.6072E3858D1E@sourceware.org> (raw)

https://gcc.gnu.org/g:b79c973bddadb6ac8103c73a85025c997576415d

commit b79c973bddadb6ac8103c73a85025c997576415d
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Thu Sep 8 14:01:14 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.
    
    (cherry picked from commit 741478ed3ed51658af476bccbc198da931e41d44)

Diff:
---
 libgomp/ChangeLog.omp | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/libgomp/ChangeLog.omp b/libgomp/ChangeLog.omp
index acbcd39cb6d..b5075dfec57 100644
--- a/libgomp/ChangeLog.omp
+++ b/libgomp/ChangeLog.omp
@@ -1,3 +1,11 @@
+2022-09-08  Tobias Burnus  <tobias@codesourcery.com>
+
+	Backport from mainline:
+	2022-05-17  Jakub Jelinek  <jakub@redhat.com>
+
+	* libgomp.texi (OpenMP 5.1): Remove "Not inside target regions"
+	comment for omp_display_env feature.
+
 2022-09-05  Tobias Burnus  <tobias@codesourcery.com>
 
 	Backport from mainline:

                 reply	other threads:[~2022-09-08 12:25 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=20220908122524.6072E3858D1E@sourceware.org \
    --to=burnus@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).