https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93289
--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> --- On Thu, Jan 16, 2020 at 05:14:44PM +0000, burnus at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93289 > > --- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> --- > Okay, it is indeed a -std=gnu extension. I still regard it as bug that it > differs, but we can now think about which one to change. Namely: IMHO, yes, it is a bug. I have come to believe that anything that is an extension should emit a error/warning. This includes defacto standard things like REAL*4, where a new -fallow-invalid-typespec would accept REAL*4 with a warning and -Winvalid-typespec could be used to suppress the warning. FOr this particular bug, you also need to look in array.c. For example, in gfc_match_array_constructor(), gfortran walks the constructor to check for compatible typespecs of constructor components if a type spec is present (ie., [real(4) :: x, y]). See lines 1292-1332. The is also the function walk_array_constructor().
