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 r12-3541] Add OpenACC 'host_data' testing to 'gfortran.dg/goacc/unexpected-end.f90'
Date: Wed, 15 Sep 2021 08:26:40 +0000 (GMT)	[thread overview]
Message-ID: <20210915082640.3C8AB3857C6F@sourceware.org> (raw)

https://gcc.gnu.org/g:8b69c481fc86e04c6c83f3a49eef2760c175a8f2

commit r12-3541-g8b69c481fc86e04c6c83f3a49eef2760c175a8f2
Author: Thomas Schwinge <thomas@codesourcery.com>
Date:   Wed Sep 15 10:25:53 2021 +0200

    Add OpenACC 'host_data' testing to 'gfortran.dg/goacc/unexpected-end.f90'
    
    Use underscore instead of space in 'host_data'.
    
    Follow-up to recent commit 33fdbbe4ce6055eb858096d01720ccf94aa854ec
    "Fortran: Add missing ST_OMP_END_SCOPE handling [PR102313]".
    
            gcc/testsuite/
            * gfortran.dg/goacc/unexpected-end.f90: Add OpenACC 'host_data'
            testing.

Diff:
---
 gcc/testsuite/gfortran.dg/goacc/unexpected-end.f90 | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/gcc/testsuite/gfortran.dg/goacc/unexpected-end.f90 b/gcc/testsuite/gfortran.dg/goacc/unexpected-end.f90
index 442724fea83..e9db47b3270 100644
--- a/gcc/testsuite/gfortran.dg/goacc/unexpected-end.f90
+++ b/gcc/testsuite/gfortran.dg/goacc/unexpected-end.f90
@@ -4,7 +4,7 @@
 
 !$acc end DATA  ! { dg-error "Unexpected !.ACC END DATA" }
 
-!$acc end HOST DATA  ! { dg-error "Unclassifiable OpenACC directive" }
+!$acc end HOST_DATA  ! { dg-error "Unexpected !.ACC END HOST_DATA" }
 
 !$acc end KERNELS  ! { dg-error "Unexpected !.ACC END KERNELS" }
 
@@ -20,4 +20,6 @@
 
 !$acc end SERIAL LOOP  ! { dg-error "Unexpected !.ACC END SERIAL LOOP" }
 
+!$acc end EUPHORBIA LATHYRIS  ! { dg-error "Unclassifiable OpenACC directive" }
+
 end


                 reply	other threads:[~2021-09-15  8:26 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=20210915082640.3C8AB3857C6F@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).