http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51991
--- Comment #10 from Sebastien Bardeau <bardeau at iram dot fr> 2012-02-08
10:38:42 UTC ---
I checked the gfortran trunk revision 183991 and the "bug" does not seem to be
fixed. I can also add that the DATA*-named variables give also erroneous
messages.
gfortran -v:
Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/home/bardeau/Softs/gcc-4.7.0-20120208/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.7.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc-trunk-source/gcc/configure
--enable-languages=c,c++,fortran --enable-checking=release --disable-bootstrap
--disable-libmudflap --enable-libgomp --enable-lto --enable-gold
--with-plugin-ld=/usr/bin/gold --prefix=/usr/local/gcc-trunk
Thread model: posix
gcc version 4.7.0 20120208 (experimental) [trunk revision 183991] (GCC)
code:
subroutine sav
integer :: save1
save1 = something wrong
end subroutine sav
!
subroutine dat
integer :: data1
data1 = something wrong
end subroutine dat
messages:
gfortran-error4.f90:3.6:
save1 = something wrong
1
Error: Syntax error in SAVE statement at (1)
gfortran-error4.f90:8.6:
data1 = something wrong
1
Error: Syntax error in DATA statement at (1)
