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-11] c-c++-common/gomp/map-6.c: Fix dg-error due to mapping changes
Date: Fri, 14 May 2021 11:57:06 +0000 (GMT)	[thread overview]
Message-ID: <20210514115706.110CD386FC32@sourceware.org> (raw)

https://gcc.gnu.org/g:17c55806b3777b12904bd4704c667a1707f9bb62

commit 17c55806b3777b12904bd4704c667a1707f9bb62
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Fri May 14 13:41:52 2021 +0200

    c-c++-common/gomp/map-6.c: Fix dg-error due to mapping changes
    
    OpenMP 5 relaxed some repetition rules such that some double-use
    warnings no longer occur; that patch is not yet on mainline.
    
    gcc/testsuite/
            * c-c++-common/gomp/map-6.c: Remove two dg-error.

Diff:
---
 gcc/testsuite/c-c++-common/gomp/map-6.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/testsuite/c-c++-common/gomp/map-6.c b/gcc/testsuite/c-c++-common/gomp/map-6.c
index 6ee59714847..194e9e070eb 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)  /* { dg-error "'always' appears more than once in map clauses" } */
+  #pragma omp target map (always, always)  /* 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, always, close)  /* Note: 'always' appears more than once in map clauses */
   ;
 
   #pragma omp target map (always, close, to: always, close, b7)


                 reply	other threads:[~2021-05-14 11:57 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=20210514115706.110CD386FC32@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).