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/null_1.f90 | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 gcc/testsuite/gfortran.dg/null_1.f90 (limited to 'gcc/testsuite/gfortran.dg/null_1.f90') diff --git a/gcc/testsuite/gfortran.dg/null_1.f90 b/gcc/testsuite/gfortran.dg/null_1.f90 new file mode 100644 index 000000000..d367bb3de --- /dev/null +++ b/gcc/testsuite/gfortran.dg/null_1.f90 @@ -0,0 +1,19 @@ +! { dg-do compile } +! PR fortran/20858 +! If we have "x = null(i)", then "null()" acquires the type, kind type, +! and rank of i and these need to match those of x. +program null_1 + integer, parameter :: sp = kind(1.e0), dp = kind(1.d0) + integer, pointer :: i => null() + real(sp), pointer :: x => null() + real(dp), pointer :: y => null() + real(sp), pointer :: z(:) => null() + x => null(i) ! { dg-error "types in pointer assignment" } + x => null(y) ! { dg-error "types in pointer assignment" } + z => null(i) ! { dg-error "types in pointer assignment" } + z => null(y) ! { dg-error "types in pointer assignment" } + x => null(z) ! { dg-error "ranks in pointer assignment" } + z => null(x) ! { dg-error "ranks in pointer assignment" } + z => null(z) + nullify(i, x, y, z) +end program null_1 -- cgit v1.2.3