https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108369
--- Comment #22 from kargls at comcast dot net --- On 2/25/25 20:28, jvdelisle at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108369 > > --- Comment #21 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- > (In reply to kargls from comment #20) >> (In reply to Jerry DeLisle from comment #19) >>> >>> What this is doing is invoking -std=legacy for files with suffixes that >>> imply legacy files such as .f >>> >>> This is my first dive on the lang-spec file so there may be something a >>> little different we do. >> >> The .f suffix denotes fixed-form source code, which is independent >> of what -std=legacy originally meant. The -std=legacy allows a bunch >> of nonstandard Fortran or deleted features. IMO, it should not be >> used as a hammer. >> > It breaks some test cases as well. At this point I am undecided bewteen > changing this or adding to the documentation that -std=legacy may be needed > when using -x f77 and leave everything alone. > I think documenting that the '-x f77' option may also require the '-std=legacy' option is decent solution. If the '-x f77' was added by g77, the we could state that requirements from newer standards leads to the need to -std=legacy.
