From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 040173858D35; Sat, 9 Sep 2023 11:00:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 040173858D35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1694257205; bh=bqmtIkb+CLpyQBgqwVG+BWXA8yunEgrOR+hZmC9YprE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=M5WQL9Y3h+Uw+uX89tWsgRpaqD+wvS/ir3r7AwyqKL4Ixv68no0KmbVVN7AUsbXPh qI+rmmXwN7QKOXaFXFmjG+CHOxsg+xHF4ht7MNuRgikV8nfP9lhC2upiFu+cs+91R5 LLtAant9o8rpeliH9bDmdKsqpDJT765bLpXVv42I= From: "pault at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/97122] Spurious FINAL ... must be in the specification part of a MODULE Date: Sat, 09 Sep 2023 11:00:03 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 11.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: pault at gcc dot gnu.org X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 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=3D97122 --- Comment #13 from Paul Thomas --- (In reply to anlauf from comment #12) > Fixed on mainline for gcc-14. >=20 > Shall we close it? Or does it deserve backporting? Hi Harald, I was considering a backport of a composite finalization patch to bring 13-branch up to the same state as trunk. Since 13.2 has been released, this= , or fairly soon, seems like a good time to do it. I am 200% tied up in daytime work for another two weeks and will return to = this and completion of the associate work then. Cheers Paul=