https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88190
--- Comment #6 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- (In reply to Dominique d'Humieres from comment #0) > While playing with pr88052 I have found that the value of > compile_options.allow_std passed to libgfortran is the same (4095) when > compiling with -std=gnu or -std=legacy. > 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. This way we dont mess around with all existing behaviors that people are use to. Then for the few cases where we want it we can define a new macro as: #define GFC_LEGACY_ONLY (compile_options.warn_std == 0) and use that in the unique case of pr78351. Just some thoughts to avoid major ripple.
