From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CBFA03858D34; Wed, 8 Jul 2020 20:12:32 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CBFA03858D34 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1594239152; bh=oJTuyd1OXGPlpimd0aMwQaYYDbiNrt90ODTaLjxAyD0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=hng4GyaZDSu809A1O8s3V8Ydi2QS1R3mZg4p2zyE61SobzfofZQda10aa7eagORtP RIHkhgo6tL8J4pcEAE8wEbiANyKWhiz+HS3izodK8uSEk79XERMJ4yYjJziD0Gqpqn T0w6az8ifx8K6ZBYKvOsVuqX/DFdLUiKWuNraMeM= From: "abensonca at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/96122] Segfault when using finalizer Date: Wed, 08 Jul 2020 20:12:32 +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: X-Bugzilla-Severity: normal X-Bugzilla-Who: abensonca at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jul 2020 20:12:32 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96122 --- Comment #2 from Andrew Benson --- (In reply to Dominique d'Humieres from comment #1) > Confirmed. For me it segfaults from GCC7 up to GCC11. Interesting. This started occurring for me when I updated from GCC10.1 to 1= 1. But, the code I posted is a reduced test case that I created - so maybe the original (non-reduced-test-case) code wasn't triggering this previously for some reason.=