From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 4EC613858D3C; Sat,  8 Apr 2023 13:00:05 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4EC613858D3C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1680958805;
	bh=RnNYilbiVzFJfEFajoWT3UK6uFldV4JFuvlEtHeaQmk=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=rEGu1rV29ZZVFCeVbCe2uKUC8b20Naw407GdGhALxggm2EwbhenqYysrMzy8swuMG
	 O7k8Cc9SrVg3706BdtiFdHit9kb7dk6CHXES5xmDV1E13Z0Ir8LLnbcL4R2zThbzGc
	 GcGfDM3iYXe1KSrGNpDUgutNA0WlwuTHmxO9hOm8=
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/102111] Segfault with associate to derived type with
 allocatable component
Date: Sat, 08 Apr 2023 13:00:04 +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.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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: resolution bug_status
Message-ID: <bug-102111-4-eJlMGL0jCz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-102111-4@http.gcc.gnu.org/bugzilla/>
References: <bug-102111-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D102111

Paul Thomas <pault at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #4 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to anlauf from comment #3)
> I get a memory corruption on x86_64-pc-linux-gnu when adding a print
> as in comment#1.
>=20
> valgrind complains about:
>=20
> Invalid free() / delete / delete[] / realloc()
>=20
> So I guess it is not (fully) fixed yet.

It's fixed on mainline now.

Cheers

Paul=