summaryrefslogtreecommitdiff
path: root/gcc/testsuite/gfortran.dg/data_char_2.f90
diff options
context:
space:
mode:
authorupstream source tree <ports@midipix.org>2015-03-15 20:14:05 -0400
committerupstream source tree <ports@midipix.org>2015-03-15 20:14:05 -0400
commit554fd8c5195424bdbcabf5de30fdc183aba391bd (patch)
tree976dc5ab7fddf506dadce60ae936f43f58787092 /gcc/testsuite/gfortran.dg/data_char_2.f90
downloadcbb-gcc-4.6.4-554fd8c5195424bdbcabf5de30fdc183aba391bd.tar.bz2
cbb-gcc-4.6.4-554fd8c5195424bdbcabf5de30fdc183aba391bd.tar.xz
obtained gcc-4.6.4.tar.bz2 from upstream website;upstream
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.
Diffstat (limited to 'gcc/testsuite/gfortran.dg/data_char_2.f90')
-rw-r--r--gcc/testsuite/gfortran.dg/data_char_2.f9014
1 files changed, 14 insertions, 0 deletions
diff --git a/gcc/testsuite/gfortran.dg/data_char_2.f90 b/gcc/testsuite/gfortran.dg/data_char_2.f90
new file mode 100644
index 000000000..26e31a14f
--- /dev/null
+++ b/gcc/testsuite/gfortran.dg/data_char_2.f90
@@ -0,0 +1,14 @@
+! { dg-do run }
+! { dg-options "-std=legacy" }
+!
+! Test that getting a character from a
+! string data works.
+
+CHARACTER*10 INTSTR
+CHARACTER C1
+DATA INTSTR / '0123456789' /
+
+C1 = INTSTR(1:1)
+if(C1 .ne. '0') call abort()
+
+end