[Bug fortran/114611] H edit descriptor should flag as error with -std-f95 (or higher)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114611 --- Comment #2 from Walter Spector --- Revisiting this, I still think that by the definition of the default -std=gnu, the compiler should give a warning by default, and give an error when -std=f95 (or higher) is specified. Currently no warning

[Bug fortran/119856] Missing commas in I/O formats not diagnosed by default at compile time.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119856 --- Comment #12 from Walter Spector --- > Definately not right. > > This is some different Issue. If it would help, I'd be happy to submit another PR.

[Bug fortran/119856] Missing commas in I/O formats not diagnosed by default at compile time.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119856 --- Comment #10 from Walter Spector --- My bad. Didn't have LD_LIBRARY_PATH set right... $ ls -l $LD_LIBRARY_PATH/*gf* -rw-r--r-- 1 root root 21336066 May 29 07:59 /usr/local/lib64/libgfortran.a -rwxr-xr-x 1 root root 977 May 29 07:59 /us

[Bug fortran/119856] Missing commas in I/O formats not diagnosed by default at compile time.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119856 --- Comment #7 from Walter Spector --- Confirmed that the compiler now diagnoses the missing commas. Thanks! As noted in Comment 1, there is no message at run-time for run-time formats: $ cat badfmt2.f90 program badfmt implicit none char

[Bug fortran/119856] Missing commas in I/O formats not diagnosed by default at compile time.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119856 --- Comment #2 from Walter Spector --- Having suffered through porting Fortran programs from one compiler to another, and one system to another, uncountable times over the past 50 years, I am one who doesn't like "legacy" extensions to be enable

[Bug fortran/119856] New: Missing commas in I/O formats not diagnosed by default at compile time.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119856 Bug ID: 119856 Summary: Missing commas in I/O formats not diagnosed by default at compile time. Product: gcc Version: 16.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/114611] New: H edit descriptor should flag as error with -std-f95 (or higher)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114611 Bug ID: 114611 Summary: H edit descriptor should flag as error with -std-f95 (or higher) Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/77504] [11/12/13/14 Regression] "is used uninitialized" with allocatable string and array constructors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77504 Walter Spector changed: What|Removed |Added CC||w6ws at earthlink dot net --- Comment #

[Bug fortran/57360] Implement a warning for implied save

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57360 --- Comment #9 from Walter Spector --- It appears that Lfortran issues a message for this case. See: https://github.com/j3-fortran/fortran_proposals/issues/83#issuecomment-1906266587

[Bug fortran/57360] Implement a warning for implied save

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57360 --- Comment #8 from Walter Spector --- Hi, It is a good point. The message is helpful when issued within a procedure. At module scope, it doesn't mean much since everything at that level is SAVE anyway. This is similar to what happens in C:

[Bug fortran/57360] Implement a warning for implied save

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57360 --- Comment #5 from Walter Spector --- IMHO this should be a "surprising" warning when -Wsurprising is specified. The message should suggest adding an explicit SAVE attribute to make the code clear.