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 8003E3858D3C; Sun,  7 May 2023 22:10:39 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8003E3858D3C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1683497439;
	bh=QGEle+Zf0dSgL8opWw494ORov0+RKcgd1NX6fn+ts+Y=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=yqU3G4dVZBWDwxafI69cKkWK8/MDc0ihVMDRvnJJMP+oZ4ZXBmYyRzMmfc8Qm/9tD
	 lFGxVOe/V6BVD+t8SD6mPsXGYoTEO/sxNDy0XlZkbHiCWb5ubi9SGpBBLIhNpMCtqo
	 2GBZewTs2kjpsUpdj1Q8NybUhK948Qd+Tev2nc48=
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: Sun, 07 May 2023 22:10:39 +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: RESOLVED
X-Bugzilla-Resolution: FIXED
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-36sdOI1o61@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 #16 from john.harper at vuw dot ac.nz ---
Saw this only after my previous 2 replies, A semicolon in a namelist is=20
not a separator between Fortran statements, but it takes the place of a=20
comma between values when decimal=3D'COMMA' in an open, read or write=20
statement according to f2003 10.9 and 10.10, and 9.5.1 C928 says decimal=3D=
=20
and nml=3D may both appear in a data transfer statement.

John

On Sun, 7 May 2023, jvdelisle at gcc dot gnu.org wrote:

> Date: Sun, 7 May 2023 18:35:46 +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 accepted=
 it
> Resent-Date: Mon, 8 May 2023 06:36:00 +1200 (NZST)
> Resent-From: <john.harper@vuw.ac.nz>
>=20
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109662
>
> --- Comment #13 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
> (In reply to Jerry DeLisle from comment #12)
>
> That recent patch regression tests fine. I should mention, there is one o=
f our
> original test cases in gfortran.dg that does use a comma. We definitely h=
ave
> see the comma used, but I have never seen a semi-colon.  I think because =
it is
> a newer feature allowing semicoln separators between FORTRAN statements o=
n a
> single line. (?)
>
> Regardless, I am ready to push this out to trunk.
>
> --=20
> You are receiving this mail because:
> You reported the bug.
>


-- 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=