https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88190
--- Comment #7 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- > I have been giving this some thought. After reading our current documentation > for -std= why do we all of a sudden change a policy because the reporter of > 88052 does not like something? Why not just keep the current behavior and use > the allow_std for pr88052 and allow the extension with -std=gnu and default. > Then when user wants more rigorous compliance then use -std=f95, etc. as is > done now. Agreed! However I think it is not a good idea to keep gfc_option.allow_std the same for -std=gnu and std=legacy. This will allow to reject some legacy codes that should be fixed: dangerous extensions, easy to fix ones, ... My list in (weak) priority order is (1) AC-IMPLIED-DO (2) SAVE statement (3) PARAMETER without () (4) REAL array (5) Duplicate .* attribute (6) Label not in the same block (6) Hollerith ...
