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 6272E3856089; Fri, 28 Jul 2023 07:59:28 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6272E3856089
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1690531168;
	bh=EWRAxsTfc7AGBsyktGUZ9ZPGFj2ejRgOPAbVxjxmwHo=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=wUB1hBS0l0H4Tt7gC+pSOlBmtXbvot6gBOIqmrqUCdj5Bm4uWBZbGfpiIv5XrLhd/
	 kRuybDzrYSiKip77ktNUmJSZopx+C04X93dEVG1aKeFDjjL7O0wU031G9VOHsueGap
	 b9vRIQNIWMf1YcLluK6q/Tx2MIvjstwrX0OVg8FY=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110838] [14 Regression] wrong code on
 x365-3.5, -O3, sign extraction
Date: Fri, 28 Jul 2023 07:59:28 +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: rguenth at gcc dot gnu.org
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-110838-4-OTu0cUzpnp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110838-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110838-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=3D110838

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
=3D> 0x00000000004009ae <+126>:   ud2=20=20=20=20

confirmed.

(gdb) p dst_ok
$1 =3D "\001\377\001\377\001\001\377\377\001"
(gdb) p dst
$2 =3D "\001\000\001\000\001\001\000\000\001"

I think we have a bug somewhere about a bug in pattern matching with a wide=
ning
op.=