Currently, it is far from obvious that rejected code might be compilable with
-std=legacy/-fno-range-check or similar (is there anything else?). I think one
could add a note to the error message:
Examples:
"Integer too big for its kind at %C" -> "Integer too big for its kind at %C.
Use -fno-range-check to disable this check"
"Duplicate PROTECTED attribute specified at %L" -> "Duplicate PROTECTED
attribute specified at %L. Use -std=legacy to disable this check"
If one does so, one might also consider to promote some of the STD_GNU to
STD_LEGACY. My candidate would be, e.g., re-typing of used symbols ("use a,
only: sym; integer sym").
--
Summary: RFC: legacy-only allowed: State that code is allowed
with -std=legacy ?
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: burnus at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31601
