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 16C763858C1F; Wed, 14 Jun 2023 21:09:36 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 16C763858C1F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1686776976;
	bh=i3Dxh8MeuILJ3qrVLn407OtBqHBf+PhA/nA/GbYHBl4=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=ffjoRk5BviPKclpf+AW6KmjwdPtXIQ/YWd4mMv9OYVaeguVZqccfXwFSpPgI+emaj
	 MP7ViHdFn+UlbpuVl6c3/FoFss8evCPOEIhc2x3tXOuUx2bI5a5MLel2/OZV7sWd/S
	 0b8Uu4uPrPb7wNQz6XpajYutyutRG5E3Ns78QTu4=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110252] [14 Regression] Wrong code at -O2/3/s
 on x86_64-linux-gnu
Date: Wed, 14 Jun 2023 21:09:35 +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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-110252-4-QftIxke3q1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110252-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110252-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=3D110252

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Created attachment 55323
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D55323&action=3Dedit
Patch which fixes this issue

This patch fixes the issue by temporary removing the flow sensitive informa=
tion
on the statement that will be moved while trying out match-and-simplify.

We don't want to remove the flow sensitive information always because if we
don't decide to move it in the end, we just lost it.
I am not the best at naming things so the name of the class will most likely
change before I submit the patch. But I wanted to give a preview here.
Note this is a latent bug in phiopt since the match-and-simplify usage was
added really; just only recently has been noticed due to range information
being used more in match.=