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 81AD33858D37; Fri, 22 Sep 2023 14:56:33 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 81AD33858D37
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1695394593;
	bh=L+nGe3sihAAH/NrqMlSP4GbE3pkoNMNj1ovP6eoWB3A=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=bdBZGQpmL5HUWzRfMUJyl0ad5gC6yQlrl0aET4sysYZiVpHIFZq+qnq6WqVmYjQNI
	 Ou855gXvX63fY2KMMo/4wEv0dzlwOKD8i4u4BrI21TnIrXC9rM6OlLEGd6Hx5yUTwp
	 eyt4SeMiDRL4ZeJ7wfgRBzTCUZP5AXZuUV3dsj6g=
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110311] [14 Regression] regression in
 tree-optimizer
Date: Fri, 22 Sep 2023 14:56:30 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
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: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-110311-4-BptMXqVCGH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110311-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110311-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=3D110311

--- Comment #56 from J=C3=BCrgen Reuter <juergen.reuter at desy dot de> ---
What do we do now? We know the offending commit, and the commit that fixed =
(or
"fixed") it. Closing? Do we understand what happened here, so why it went w=
rong
and why it got fixed?=