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 4A4613858D33; Wed,  9 Aug 2023 09:02:15 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4A4613858D33
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1691571735;
	bh=COtPz6S0+PMl0He2a9/igdeHDfSAn5W/LwP4xckSCks=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Yk7gSmIBq3YDv95QeXGMy+JvXTMZfCUOkeCsLZXLmj6DWqqySBj0mEOkR8ZVCcBfF
	 5dhIC+815tfZgISgrKs2PLePl8iKFTMY8QePUrHyE2AJSrjtJTOPPlJ53lOR6MHkRs
	 zKqbuvvEl7peq6ZjfchOy8hcw0wZm+IetaiW0Qcg=
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: Wed, 09 Aug 2023 09:02:14 +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-TiW7bHLhdU@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 #50 from J=C3=BCrgen Reuter <juergen.reuter at desy dot de> ---
How to proceed here? Since almost exactly a month the current gcc git master
doesn't show this problem anymore, from our CI I can deduce that the versio=
n on
July 3rd still failed, while the version on July 10th worked again. Since t=
hen
the problem didn't show up again. My guess is that something has changed in=
 the
optimizer again (maybe because of a different problem/regression). Is it wo=
rth
to find the offending commit and see when and how it was fixed (maybe even
accidentally), or shall we add a gcc testsuite for regression testing, and
close this issue?=