From: Tobias Burnus <Tobias_Burnus@mentor.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Subject: [Patch, committed] gfortran.dg/gomp/requires-4.f90: Fix !$omp syntax
Date: Fri, 27 Nov 2020 11:50:07 +0100 [thread overview]
Message-ID: <436d1834-cf60-e3af-209c-f1a2f8a96b2c@mentor.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]
Found when grepping & post commit. There were two !$omp issues in
the testcase – which (currently) do not show up due to the previous
(and intended) errors.
Tobias
-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander Walter
[-- Attachment #2: committed.diff --]
[-- Type: text/x-patch, Size: 1750 bytes --]
commit 6fb9b4c97690c5750e49c32fa2a373a7c66c5d46
Author: Tobias Burnus <tobias@codesourcery.com>
Date: Fri Nov 27 11:45:14 2020 +0100
gfortran.dg/gomp/requires-4.f90: Fix !$omp clause
gcc/testsuite/
* gfortran.dg/gomp/requires-4.f90: Fix typo in '!$omp' clause.
diff --git a/gcc/testsuite/gfortran.dg/gomp/requires-4.f90 b/gcc/testsuite/gfortran.dg/gomp/requires-4.f90
index 0dc5e69da04..b17aceb898b 100644
--- a/gcc/testsuite/gfortran.dg/gomp/requires-4.f90
+++ b/gcc/testsuite/gfortran.dg/gomp/requires-4.f90
@@ -30,7 +30,7 @@ contains
!$omp end target
end subroutine
subroutine bar
- !$omp requires unified_addres ! { dg-error "must appear in the specification part of a program unit" }
+ !$omp requires unified_address ! { dg-error "must appear in the specification part of a program unit" }
end subroutine bar
end
! { dg-prune-output "not yet supported" }
commit d78e106e95191f44274c8c9ba196abd6fd5ed558
Author: Tobias Burnus <tobias@codesourcery.com>
Date: Fri Nov 27 11:40:11 2020 +0100
gfortran.dg/gomp/requires-4.f90: Fix !$omp syntax
gcc/testsuite/
* gfortran.dg/gomp/requires-4.f90: Fix '!$omp' syntax.
diff --git a/gcc/testsuite/gfortran.dg/gomp/requires-4.f90 b/gcc/testsuite/gfortran.dg/gomp/requires-4.f90
index e0eb4dbc603..0dc5e69da04 100644
--- a/gcc/testsuite/gfortran.dg/gomp/requires-4.f90
+++ b/gcc/testsuite/gfortran.dg/gomp/requires-4.f90
@@ -26,8 +26,8 @@ program main
!$omp requires reverse_offload
contains
subroutine foo
- !$target
- !$end target
+ !$omp target
+ !$omp end target
end subroutine
subroutine bar
!$omp requires unified_addres ! { dg-error "must appear in the specification part of a program unit" }
reply other threads:[~2020-11-27 10:50 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=436d1834-cf60-e3af-209c-f1a2f8a96b2c@mentor.com \
--to=tobias_burnus@mentor.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).