From: Cesar Philippidis <cesar@codesourcery.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Fortran List <fortran@gcc.gnu.org>,
Chung-Lin Tang <cltang@codesourcery.com>
Subject: Re: [gomp4] add support for fortran allocate support with declare create
Date: Thu, 06 Apr 2017 14:26:00 -0000 [thread overview]
Message-ID: <6680d010-6b7c-6905-650d-7e450a218363@codesourcery.com> (raw)
In-Reply-To: <87bms9hpof.fsf@euler.schwinge.homeip.net>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
On 04/06/2017 02:05 AM, Thomas Schwinge wrote:
>> --- /dev/null
>> +++ b/gcc/testsuite/gfortran.dg/goacc/declare-allocatable-1.f90
>> @@ -0,0 +1,25 @@
>> +! Verify that OpenACC declared allocatable arrays have implicit
>> +! OpenACC enter and exit pragmas at the time of allocation and
>> +! deallocation.
>> +
>> +! { dg-additional-options "-fdump-tree-original" }
>> +[...]
>> +! { dg-final { scan-tree-dump-times "pragma acc enter data map.declare_allocate" 1 "gimple" } }
>> +! { dg-final { scan-tree-dump-times "pragma acc exit data map.declare_deallocate" 1 "gimple" } }
>
> UNRESOLVED: gfortran.dg/goacc/declare-allocatable-1.f90 -O scan-tree-dump-times gimple "pragma acc enter data map.declare_allocate" 1
> UNRESOLVED: gfortran.dg/goacc/declare-allocatable-1.f90 -O scan-tree-dump-times gimple "pragma acc exit data map.declare_deallocate" 1
> PASS: gfortran.dg/goacc/declare-allocatable-1.f90 -O (test for excess errors)
>
> "original" vs. "gimple" -- which one should it be?
I'm bad at noticing new unresolved test cases.
It could be either, but I changed it to original to ensure that the
fortran FE inserts those acc enter/exit data directives appropriately.
This patch has been committed to gomp-4_0-branch.
Cesar
[-- Attachment #2: gomp4-declare-test.diff --]
[-- Type: text/x-patch, Size: 896 bytes --]
2017-04-06 Cesar Philippidis <cesar@codesourcery.com>
gcc/testsuite/
* gfortran.dg/goacc/declare-allocatable-1.f90: Correct test.
diff --git a/gcc/testsuite/gfortran.dg/goacc/declare-allocatable-1.f90 b/gcc/testsuite/gfortran.dg/goacc/declare-allocatable-1.f90
index 9195055..b6bb6b3 100644
--- a/gcc/testsuite/gfortran.dg/goacc/declare-allocatable-1.f90
+++ b/gcc/testsuite/gfortran.dg/goacc/declare-allocatable-1.f90
@@ -21,5 +21,5 @@ program allocate
deallocate (a)
end program allocate
-! { dg-final { scan-tree-dump-times "pragma acc enter data map.declare_allocate" 1 "gimple" } }
-! { dg-final { scan-tree-dump-times "pragma acc exit data map.declare_deallocate" 1 "gimple" } }
+! { dg-final { scan-tree-dump-times "pragma acc enter data map.declare_allocate" 1 "original" } }
+! { dg-final { scan-tree-dump-times "pragma acc exit data map.declare_deallocate" 1 "original" } }
next prev parent reply other threads:[~2017-04-06 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 15:24 Cesar Philippidis
2017-04-06 9:05 ` Thomas Schwinge
2017-04-06 14:26 ` Cesar Philippidis [this message]
2022-11-02 20:04 ` Add 'libgomp.oacc-fortran/declare-allocatable-1.f90' (was: [gomp4] add support for fortran allocate support with declare create) Thomas Schwinge
2022-11-02 20:10 ` Add 'libgomp.oacc-fortran/declare-allocatable-1-runtime.f90' (was: Add 'libgomp.oacc-fortran/declare-allocatable-1.f90') Thomas Schwinge
2022-11-02 20:15 ` Add 'libgomp.oacc-fortran/declare-allocatable-array_descriptor-1-runtime.f90' Thomas Schwinge
2022-11-02 20:22 ` Support OpenACC 'declare create' with Fortran allocatable arrays, part I [PR106643] Thomas Schwinge
2022-11-02 20:34 ` Support OpenACC 'declare create' with Fortran allocatable arrays, part II [PR106643, PR96668] (was: Support OpenACC 'declare create' with Fortran allocatable arrays, part I [PR106643]) Thomas Schwinge
[not found] ` <1ECCE9C8-0CE9-46EA-A0F2-3F3FA50F4681@gmail.com>
2022-11-03 10:47 ` Add 'libgomp.oacc-fortran/declare-allocatable-1.f90' (was: [gomp4] add support for fortran allocate support with declare create) Thomas Schwinge
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=6680d010-6b7c-6905-650d-7e450a218363@codesourcery.com \
--to=cesar@codesourcery.com \
--cc=cltang@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=thomas@codesourcery.com \
/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).