From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E1E0B3858C5E; Wed, 17 May 2023 20:35:33 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E1E0B3858C5E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1684355733; bh=cRqc5P0OMGX4wK2id6DGpjdzVPlefSdefRkdjTjjaCs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ZFL/+mS0vDdIFA6RwELt+Bzru8jnJzAhUPI/SFslG9x01jdPTMt9hF7hqn36WmyLI mlFVsAFZcss/paZLvaTiSb7hBmibeJ2TLxaAgNlnED9e8KQTtLF9RYLE0SRfJv7qcZ vW9ih+QCzdqD8FuFzc9uasyRh+ylC7Y+2+9dbJas= From: "W.H.Ball at bham dot ac.uk" To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/109897] Incorrect bad namelist object reported in error message when bad data appears after a valid array component Date: Wed, 17 May 2023 20:35: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.3.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: W.H.Ball at bham dot ac.uk X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P5 X-Bugzilla-Assigned-To: unassigned 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=3D109897 --- Comment #2 from W.H.Ball at bham dot ac.uk --- > Can you confirm this? Yes, I get the same. I also get a nicer error message with -std=3Df2008. Thanks for finding this, since that's already a potential workaround I can investigate in the code that prompted this.=