From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C48993858D1E; Wed, 17 May 2023 20:28:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C48993858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1684355295; bh=+5iKEp+LGyjEB8zeQOGu1CpXxdPos5Y2zPczU3SOeG4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=rethP6HyVc2LD9aWeqRFkHv6J2NL9zJ41j1QeHRlGCIs7tpmME8inUR/8QVml88bS enlfG9EoNL/Ye5DKo4xkeGlcWf/WPCBdtc8fr0qZe5w6N2yrHyyKUyOtnkXZI6i4oO Zw4XUcBedYvBWeeBE4UwoRYK3d2NltnREpbbo2IA= From: "anlauf at gcc dot gnu.org" 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:28:15 +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: anlauf at gcc dot gnu.org 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: component priority cf_reconfirmed_on bug_severity 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 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Component|fortran |libfortran Priority|P3 |P5 Last reconfirmed| |2023-5-17 Severity|normal |enhancement --- Comment #1 from anlauf at gcc dot gnu.org --- I get a nicer error message when I specify the compiler flag -std=3Df2018 on the command line: Fortran runtime error: Cannot match namelist object name bad_namelist So there might have been some attempt so support legacy stuff so that you don't get the best user experience by default. Can you confirm this?=