From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BDC1F385842C; Sun, 7 May 2023 18:35:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BDC1F385842C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1683484546; bh=ehoPJwuy/s5hTsZjqIFQgGwb5eegZTVrDIQZQnoVKzI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ZkPK+kbOWCTNY/VbfLymXN7i3EM4XlzThbzjJ88Qhk9hCV+C19iCPEwRWWn4eUphh gpWC0n/1Y5RhbvCDV9ucVzx6BTEA7EYRZQV05oqhCt4mZLvmcYOgCBAW7JMUXhkFkU 7s8Lq8NKN89yNAlaKuq3MVDzruWqogLZFoJiqap8= 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: Sun, 07 May 2023 18:35:46 +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: 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: 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 #13 from Jerry DeLisle --- (In reply to Jerry DeLisle from comment #12) That recent patch regression tests fine. I should mention, there is one of = our original test cases in gfortran.dg that does use a comma. We definitely have 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 on a single line. (?) Regardless, I am ready to push this out to trunk.=