--- Comment #6 from giese025 at umn dot edu 2010-03-10 16:07 ---
(In reply to comment #5)
(In reply to comment #4)
Not all valid FORTRAN 95 programs will compile properly when using this
option. If you want to ensure compliance with one of the FORTRAN standards,
please see
--- Comment #7 from kargl at gcc dot gnu dot org 2010-03-10 17:17 ---
(In reply to comment #6)
(In reply to comment #5)
(In reply to comment #4)
Not all valid FORTRAN 95 programs will compile properly when using this
option. If you want to ensure compliance with one of
--- Comment #1 from kargl at gcc dot gnu dot org 2010-03-09 19:40 ---
Don't use -pedantic. It forces a symmetric range on
the integer type, [-huge():huge]. This can be checked
during constant folding, and NOT(A) is detected as an
error. gfortran does not instrument the runtime code
--- Comment #2 from dominiq at lps dot ens dot fr 2010-03-09 20:45 ---
Don't use -pedantic. It forces a symmetric range on
the integer type, [-huge():huge].
This should probably be documented. Probably after
Valid Fortran 95 programs should compile properly with or without this
--- Comment #3 from kargl at gcc dot gnu dot org 2010-03-09 21:06 ---
If one is trying to adhere to a Standard then use -std=.
-pedantic simply should not be used with gfortran.
As for documenting this, see arith.c, the PR's listed
there and the mailing list.
--
kargl at gcc dot
--- Comment #4 from giese025 at umn dot edu 2010-03-10 01:17 ---
(In reply to comment #3)
If one is trying to adhere to a Standard then use -std=.
-pedantic simply should not be used with gfortran.
As for documenting this, see arith.c, the PR's listed
there and the mailing list.
--- Comment #5 from kargl at gcc dot gnu dot org 2010-03-10 03:15 ---
(In reply to comment #4)
Not all valid FORTRAN 95 programs will compile properly when using this
option. If you want to ensure compliance with one of the FORTRAN standards,
please see the -std= option.
The
