public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/omp/gcc-12] [og12] OpenACC: Don't gang-privatize artificial variables: restrict to blocks: ChangeLog
Date: Fri, 28 Oct 2022 08:44:50 +0000 (GMT)	[thread overview]
Message-ID: <20221028084451.C2A4C3857B88@sourceware.org> (raw)

https://gcc.gnu.org/g:797dde5262ced26eb47f6622e0a39831dd13f92c

commit 797dde5262ced26eb47f6622e0a39831dd13f92c
Author: Thomas Schwinge <thomas@codesourcery.com>
Date:   Fri Oct 28 10:43:24 2022 +0200

    [og12] OpenACC: Don't gang-privatize artificial variables: restrict to blocks: ChangeLog
    
    ... forgotten in og12 commit 9a50d282f03f7f1e1ad00de917143a2a8e0c0ee0
    "[og12] OpenACC: Don't gang-privatize artificial variables: restrict to blocks".

Diff:
---
 gcc/ChangeLog.omp     | 3 +++
 libgomp/ChangeLog.omp | 4 ++++
 2 files changed, 7 insertions(+)

diff --git a/gcc/ChangeLog.omp b/gcc/ChangeLog.omp
index 4bf521f2162..5859c22ccd7 100644
--- a/gcc/ChangeLog.omp
+++ b/gcc/ChangeLog.omp
@@ -1,5 +1,8 @@
 2022-10-28  Thomas Schwinge  <thomas@codesourcery.com>
 
+	* omp-low.cc (oacc_privatization_candidate_p) <DECL_ARTIFICIAL>:
+	Restrict to 'block's.
+
 	* omp-low.cc (lower_rec_simd_input_clauses): For 'ordered_max',
 	cast 'omp_max_simt_vf ()', 'omp_max_simd_vf ()' to 'unsigned'.
 
diff --git a/libgomp/ChangeLog.omp b/libgomp/ChangeLog.omp
index f31fdfe373c..396f8e7e4b4 100644
--- a/libgomp/ChangeLog.omp
+++ b/libgomp/ChangeLog.omp
@@ -1,3 +1,7 @@
+2022-10-28  Thomas Schwinge  <thomas@codesourcery.com>
+
+	* testsuite/libgomp.oacc-fortran/privatized-ref-2.f90: Adjust.
+
 2022-10-25  Abid Qadeer  <abidh@codesourcery.com>
 
 	* testsuite/libgomp.c++/usm-2.C: New test.

                 reply	other threads:[~2022-10-28  8:44 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=20221028084451.C2A4C3857B88@sourceware.org \
    --to=tschwinge@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).