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] Reverted: c-c++-common/gomp/map-6.c: Fix dg-error due to mapping changes
Date: Thu,  6 Oct 2022 09:08:34 +0000 (GMT)	[thread overview]
Message-ID: <20221006090834.7E057384C002@sourceware.org> (raw)

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

commit d8909f7d24216fcf6e734ddfd81fe3fda51d437a
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Thu Oct 6 11:00:17 2022 +0200

    Reverted: c-c++-common/gomp/map-6.c: Fix dg-error due to mapping changes
    
    Revert commit a24748da5b48f23ac83fa9f2d128f766e80567ed
    that was added to OG11 as dg-error fix for the cherry-pick of
    "Fortran/OpenMP: Add support for 'close' in map clause"
    r12-944-gcdcec2f8505ea12c2236cf0184d77dd2f5de4832
    
    2022-10-06  Tobias Burnus  <tobias@codesourcery.com>
    
            Revert:
            2021-05-14  Tobias Burnus  <tobias@codesourcery.com>
    
            * c-c++-common/gomp/map-6.c: Remove two dg-error.

Diff:
---
 gcc/testsuite/ChangeLog.omp             | 7 +++++++
 gcc/testsuite/c-c++-common/gomp/map-6.c | 4 ++--
 2 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/gcc/testsuite/ChangeLog.omp b/gcc/testsuite/ChangeLog.omp
index f9cd0ba390e..e2e0a291d21 100644
--- a/gcc/testsuite/ChangeLog.omp
+++ b/gcc/testsuite/ChangeLog.omp
@@ -1,3 +1,10 @@
+2022-10-06  Tobias Burnus  <tobias@codesourcery.com>
+
+	Revert:
+	2021-05-14  Tobias Burnus  <tobias@codesourcery.com>
+
+	* c-c++-common/gomp/map-6.c: Remove two dg-error.
+
 2022-10-06  Tobias Burnus  <tobias@codesourcery.com>
 
 	* gfortran.dg/gomp/depend-5.f90: Update scan-tree-dump.
diff --git a/gcc/testsuite/c-c++-common/gomp/map-6.c b/gcc/testsuite/c-c++-common/gomp/map-6.c
index 194e9e070eb..6ee59714847 100644
--- a/gcc/testsuite/c-c++-common/gomp/map-6.c
+++ b/gcc/testsuite/c-c++-common/gomp/map-6.c
@@ -100,10 +100,10 @@ foo (void)
   #pragma omp target map (always, close)
   ;
 
-  #pragma omp target map (always, always)  /* Note: 'always' appears more than once in map clauses  */
+  #pragma omp target map (always, always)  /* { dg-error "'always' appears more than once in map clauses" } */
   ;
 
-  #pragma omp target map (always, always, close)  /* Note: 'always' appears more than once in map clauses */
+  #pragma omp target map (always, always, close)  /* { dg-error "'always' appears more than once in map clauses" } */
   ;
 
   #pragma omp target map (always, close, to: always, close, b7)

                 reply	other threads:[~2022-10-06  9:08 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=20221006090834.7E057384C002@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).