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/read_comma.f | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 gcc/testsuite/gfortran.dg/read_comma.f (limited to 'gcc/testsuite/gfortran.dg/read_comma.f') diff --git a/gcc/testsuite/gfortran.dg/read_comma.f b/gcc/testsuite/gfortran.dg/read_comma.f new file mode 100644 index 000000000..024fceae7 --- /dev/null +++ b/gcc/testsuite/gfortran.dg/read_comma.f @@ -0,0 +1,26 @@ +! { dg-do run { target fd_truncate } } +! PR25039 This test checks that commas in input fields for formatted sequential +! reads are interpreted as the read completion. If no comma is encountered the +! normal field width determines the end of the read. The test case also checks +! that default blanks are interpreted as NULL in numerics. +! Test case derived from sample provided in PR by Iwan Kawrakow. +! Contributed by Jerry DeLisle +! + program pr25039 + implicit none + integer :: i1, i2, i3 + character(10) :: a1 + open(10, status="scratch") + write(10,'(a)') "1, 235" + rewind(10) + read(10,'(3i2)') i1,i2,i3 + if(i1.ne.1) call abort() + if(i2.ne.2) call abort() + if(i3.ne.35) call abort() + rewind(10) +! Make sure commas are read in character strings. + write(10,'(a)') "1234,6789," + rewind(10) + read(10,'(a10)') a1 + if(a1.ne."1234,6789,") call abort() + end -- cgit v1.2.3