From 554fd8c5195424bdbcabf5de30fdc183aba391bd Mon Sep 17 00:00:00 2001 From: upstream source tree Date: Sun, 15 Mar 2015 20:14:05 -0400 Subject: obtained gcc-4.6.4.tar.bz2 from upstream website; verified gcc-4.6.4.tar.bz2.sig; imported gcc-4.6.4 source tree from verified upstream tarball. downloading a git-generated archive based on the 'upstream' tag should provide you with a source tree that is binary identical to the one extracted from the above tarball. if you have obtained the source via the command 'git clone', however, do note that line-endings of files in your working directory might differ from line-endings of the respective files in the upstream repository. --- gcc/testsuite/gfortran.dg/gomp/crayptr2.f90 | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 gcc/testsuite/gfortran.dg/gomp/crayptr2.f90 (limited to 'gcc/testsuite/gfortran.dg/gomp/crayptr2.f90') diff --git a/gcc/testsuite/gfortran.dg/gomp/crayptr2.f90 b/gcc/testsuite/gfortran.dg/gomp/crayptr2.f90 new file mode 100644 index 000000000..476d7b9e7 --- /dev/null +++ b/gcc/testsuite/gfortran.dg/gomp/crayptr2.f90 @@ -0,0 +1,17 @@ +! { dg-do compile } +! { dg-options "-fopenmp -fcray-pointer" } +! { dg-require-effective-target tls } + +module crayptr2 + integer :: e ! { dg-error "CRAY POINTEE attribute conflicts with THREADPRIVATE" } + pointer (ip5, e) + +! The standard is not very clear about this. +! Certainly, Cray pointees can't be SAVEd, nor they can be +! in COMMON, so the only way to make threadprivate Cray pointees would +! be if they are module variables. But threadprivate pointees don't +! make any sense anyway. + +!$omp threadprivate (e) + +end module crayptr2 -- cgit v1.2.3