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/derived_name_2.f | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 gcc/testsuite/gfortran.dg/derived_name_2.f (limited to 'gcc/testsuite/gfortran.dg/derived_name_2.f') diff --git a/gcc/testsuite/gfortran.dg/derived_name_2.f b/gcc/testsuite/gfortran.dg/derived_name_2.f new file mode 100644 index 000000000..a89dcdfbd --- /dev/null +++ b/gcc/testsuite/gfortran.dg/derived_name_2.f @@ -0,0 +1,19 @@ +! { dg-do compile } +! PR 20897 +! Make sure intrinsic type names do not appear as names of derived types + type integer ! { dg-error "cannot be the same as an intrinsic type" } + type real ! { dg-error "cannot be the same as an intrinsic type" } + type complex ! { dg-error "cannot be the same as an intrinsic type" } + type character ! { dg-error "cannot be the same as an intrinsic type" } + type logical ! { dg-error "cannot be the same as an intrinsic type" } + type complex ! { dg-error "cannot be the same as an intrinsic type" } + type double precision ! { dg-error "cannot be the same as an intrinsic type" } + type doubleprecision ! { dg-error "cannot be the same as an intrinsic type" } + type double complex ! { dg-error "cannot be the same as an intrinsic type" } + type doublecomplex ! { dg-error "cannot be the same as an intrinsic type" } + + type x + integer y + end type x + end + -- cgit v1.2.3