[Bug fortran/36313] [F03] {MIN,MAX}{LOC,VAL} should accept character arguments

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36313 Bil Kleb changed: What|Removed |Added CC||Bil.Kleb at NASA dot gov --- Comment #7 from

[Bug fortran/53939] allows assignment to INTENT(IN) nested component

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53939 --- Comment #3 from Bil Kleb 2012-07-12 13:32:07 UTC --- OK, fair enough (and sincere thanks for taking the time to explain it). I see that if I change to the more modern ALLOCATABLE declarations, then I get a warning about assigning to an INTEN

[Bug fortran/53940] warn about duplicate USE

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53940 --- Comment #2 from Bil Kleb 2012-07-12 13:25:29 UTC --- I guess I see the USE ONLY as similar to a declaration, and to have two of the same declarations in a program is an error, e.g., $ cat duplicate_declaration.f90 << EOF program duplicate_de

[Bug fortran/53940] New: warn about duplicate USE

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53940 Bug #: 53940 Summary: warn about duplicate USE Classification: Unclassified Product: gcc Version: 4.6.2 Status: UNCONFIRMED Severity: enhancement Priority: P3

[Bug fortran/53939] New: allows assignment to INTENT(IN) nested component

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53939 Bug #: 53939 Summary: allows assignment to INTENT(IN) nested component Classification: Unclassified Product: gcc Version: 4.6.2 Status: UNCONFIRMED Severity: minor Pr