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 560453858C5E; Wed,  5 Jul 2023 07:26:52 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 560453858C5E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1688542012;
	bh=kdQS0YycY90iQz7h2m80KZ4DrtrOOCeyiWPWGpWxPBk=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=eBFnQTeWJAhuwqYGsseHXmVh3xjgP4o6xkZuTwWr5O481boIsGC/96l/Hb/nHU/2u
	 I8VuXqWa9iUSQly4OH6/8WxPrTsO6gLhZzL0gIuzicgbE2ybr1mHy8NrFNKFw0p0CG
	 vmuCtLc39dOxBE2aR/0uNILqD7VYXhWsWjNMqgd8=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/110376] Wrong code at -O1 on x86_64-linux-gnu
Date: Wed, 05 Jul 2023 07:26:51 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
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-110376-4-4kDpCuetpr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110376-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110376-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=3D110376

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #4)
> (In reply to Shaohua Li from comment #3)
> > You post a commit for fixing this bug. Does this mean this report is no=
t a
> > DUP of 110228?
>=20
> The commit was just a testcase (more testcases the better really); there
> were 3 different issues causing PR 110228 really, 2 for phiopt, one for
> ifcombine. Anyways all 3 have been fixed on the trunk. one of those 3 fix=
ed
> this issue and a testcase was added just to make sure it does not get
> exposed again.

And all three different issues should have been separate bugs ...=