From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 5C8FD3858D33; Thu,  4 May 2023 06:00:23 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5C8FD3858D33
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1683180023;
	bh=bh9X+f7j5NiypUJO9FG2Az6C9V0wW5iiHRYR4bP78OQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Ie7R2F/BffG5p4ujuyCWQCaQQQ4sxP+XDyV1twbHW8y1xZVmgBb5ebVnbgxNzQ/1T
	 UwbTSDnpXPCc3jOxXJFPdChs0fKO68/eQqAySZjBZ9U0Icwdxk54BYr/b6nUxeYwPI
	 JcSA+v7bCAXwIYVFvqApGbLEX/xuGCiMdMECro9o=
From: "john.harper at vuw dot ac.nz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/109662] bad namelist input but gfortran accepted it
Date: Thu, 04 May 2023 06:00:23 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 12.1.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: john.harper at vuw dot ac.nz
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109662-4-2tqxaOGSaG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109662-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109662

--- Comment #7 from john.harper at vuw dot ac.nz ---
I hadn't thought about -std=3Dgnu in this context but it would make sense
for std=3Dgnu to give a warning for comma after namelist name if=20
std=3Dlegacy is going to allow it without one. You wouldn't then have to=20
change the gfortran manual page.

John

On Thu, 4 May 2023, John Harper wrote:

> Date: Thu, 4 May 2023 16:59:31 +1200 (NZST)
> From: John Harper <john.harper@vuw.ac.nz>
> To: jvdelisle at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org>
> Subject: Re: [Bug libfortran/109662] bad namelist input but gfortran acce=
pted
>     it
>=20
> OK by me but I'm not in charge of gfortran!
>
> On Thu, 4 May 2023, jvdelisle at gcc dot gnu.org wrote:
>
>> Date: Thu, 4 May 2023 03:05:49 +0000
>> From: jvdelisle at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org>
>> To: John Harper <john.harper@vuw.ac.nz>
>> Subject: [Bug libfortran/109662] bad namelist input but gfortran accepte=
d=20
>> it
>> Resent-Date: Thu, 4 May 2023 15:05:59 +1200 (NZST)
>> Resent-From: <john.harper@vuw.ac.nz>
>>=20
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109662
>>=20
>> --- Comment #5 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
>> Is this acceptable:
>>=20
>> $ ./a.out
>> Compiler version =3D GCC version 14.0.0 20230424 (experimental)
>> Compiler options =3D -mtune=3Dgeneric -march=3Dx86-64 -Wpedantic
>> -fpre-include=3D/usr/include/finclude/math-vector-fortran.h
>> At line 9 of file pr109662.f90
>> Fortran runtime error: Comma after namelist name not allowed
>>=20
>> Should I allow it with -std=3Dlegacy?
>>=20
>> --=20
>> You are receiving this mail because:
>> You reported the bug.
>>=20
>
>
> -- John Harper, School of Mathematics and Statistics
> Victoria Univ. of Wellington, PO Box 600, Wellington 6140, New Zealand.
> e-mail john.harper@vuw.ac.nz phone +64(0) 4 463 5276
>


-- John Harper, School of Mathematics and Statistics
Victoria Univ. of Wellington, PO Box 600, Wellington 6140, New Zealand.
e-mail john.harper@vuw.ac.nz phone +64(0) 4 463 5276=