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 15FA63856DEC; Wed, 28 Sep 2022 14:33:25 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 15FA63856DEC
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1664375605;
	bh=lW6l0CA1xaf6/Xry7HsDfuTUo33Lq8JKESiyA7N76fA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=gldKbVHaNjzV7PcNL/T+2VgGhW1v8DefoaJGi30FUMk6VyccAVkkAIPFVi55yemLN
	 2TLhcZJ3cbz9OCpZHTpfoyAdPmrCTdihNXKtPUKwbFGXBKYGh2Lsne/mAwyng2YqT0
	 35RgwKd3Ym1R6nAfrnlEx2LI//xvEycbbtDrTioE=
From: "drfiemost at email dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/106776] Unexpected use-after-free warning
Date: Wed, 28 Sep 2022 14:33:23 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 12.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: drfiemost at email dot it
X-Bugzilla-Status: UNCONFIRMED
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: <bug-106776-4-zqqGftUOHe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106776-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=3D106776

--- Comment #2 from Leandro Nini <drfiemost at email dot it> ---
Oh, now I see it, it wasn't that obvious in the first test. But why is the
compiler allowed to postpone the store after deleting the pointer? Is there
some undefined behavior involved here or what?=