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 5D1DD3858C50; Sun, 30 Apr 2023 22:40:34 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5D1DD3858C50
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1682894434;
	bh=HW2FHNkanrr/wbWTiSunCRxs8x8an2JcItj2nloQo6Y=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=DcaWvlUlgYZh8TgEleFu9w/Q+0QQ64xZid5//2vjVH/2QFmNPkXxsGm9e9JmZdZQn
	 u4NyGJ3il8sqqHBbLIwPDQB2/zEMLBxHp4lRA9erUzN6n2x9JWS9pbYW+LNNYFTtYR
	 Uj/aAA5fKewA59QNi/pL0rAet604hxpTYb8zPFmM=
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/109662] bad namelist input but gfortran accepted it
Date: Sun, 30 Apr 2023 22:40:33 +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: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-109662-4-957Ty3iUSP@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

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kargl at gcc dot gnu.org

--- Comment #2 from kargl at gcc dot gnu.org ---
(In reply to anlauf from comment #1)
> I also interpret F2018:13.11.3.1 that a value-separator may follow only
> a name-value subsequence but not immediately the namelist-group-name.
> This is also what other brands (NAG, Intel, Nvidia) accept.
>=20
> Thus confirmed.

Yes, definitely a bug.  The issue isn't the value-separator.  It's
item (3) from 13.11.3.1.

    Input for a namelist input statement consists of

        (1) optional blanks and namelist comments,
        (2) the character & followed immediately by the
            namelist-group-name as specified in the NAMELIST
            statement,
        (3) one or more blanks,

There needs to be a blank following '&stuff'.  Now, the question
becomes "what happens with this line?"

  character(17) :: list =3D '&stuff , n =3D 666/'

The next requirement comes into play
        (4) a sequence of zero or more name-value subsequences
            separated by value separators, and

Probably should tag Jerry.=