From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2F87A3858D35; Mon, 1 May 2023 03:05:18 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2F87A3858D35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1682910318; bh=GBBnGXAdwvMwcScgfYYWfeCjbr+ZjZ7xx3gADxSRliE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=lEm7NzrLljWJuPir07+wuLbNHgIp9rd/f5dhEFATU9BPXuRzbQ/+rHHcm9UadRe1U XkzhKICRI5/y9EjpGvPI4tBs89EsbDAExPoNI6BUQnITMCwFp4JwntwcUFlkrn92hJ e6bOBNBKD/8nP9jVrROs0DyRH4Izbt+sAKok6Ms8= From: "jvdelisle at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/109662] bad namelist input but gfortran accepted it Date: Mon, 01 May 2023 03:05:17 +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: jvdelisle at gcc dot gnu.org 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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109662 --- Comment #4 from Jerry DeLisle --- I knew this looked familiar. We did it on purpose. From list_read.c: /* A trailing space is required, we give a little latitude here, 10.9.1. = */ c =3D next_char (dtp); if (!is_separator(c) && c !=3D '!') { unget_char (dtp, c); goto find_nml_name; } I think we allowed sepraators for some old legacy stuff. I will make adjustments.=