diff options
| author | upstream source tree <ports@midipix.org> | 2015-03-15 20:14:05 -0400 |
|---|---|---|
| committer | upstream source tree <ports@midipix.org> | 2015-03-15 20:14:05 -0400 |
| commit | 554fd8c5195424bdbcabf5de30fdc183aba391bd (patch) | |
| tree | 976dc5ab7fddf506dadce60ae936f43f58787092 /gcc/testsuite/gfortran.dg/fmt_error_8.f | |
| download | cbb-gcc-4.6.4-upstream.tar.bz2 cbb-gcc-4.6.4-upstream.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/fmt_error_8.f')
| -rw-r--r-- | gcc/testsuite/gfortran.dg/fmt_error_8.f | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/gcc/testsuite/gfortran.dg/fmt_error_8.f b/gcc/testsuite/gfortran.dg/fmt_error_8.f new file mode 100644 index 000000000..1d630b7db --- /dev/null +++ b/gcc/testsuite/gfortran.dg/fmt_error_8.f @@ -0,0 +1,11 @@ +! { dg-do compile } +! { dg-options "-std=f95" } +! PR35754 -std=f95: Reject "1P2E12.4" w/o a comma after the "P" +! PR +! Test case provided by Jerry DeLisle <jvdelisle@gcc.gnu.org> + character(40) :: fmt_string + write(*, '(1P2E12.4)') 1.0 ! { dg-error "Comma required" } + write(*, '(1PT12,F12.4)') 1.0 ! { dg-error "Comma required" } + write(*, '(1PE12.4)') 1.0 ! This is OK by the standard 10.1.1 + write (*,'(1PD24.15,F4.2,0P)') 1.0d0 ! This OK too. + end |