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 112E43857724; Wed,  4 Oct 2023 16:14:47 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 112E43857724
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1696436088;
	bh=uv73qjrubSGqX7JX0egrSpczNXuVU1WAeCQk5lwvQmM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=pmM9i492qiRMFlAvMR9uHfevwR8Rwquq9ScE0ggcF73fodCOEcA31Wh2mmI7QrBv/
	 PpLTJRC1p+sJ9gKQPxbTHDzuLoNmwX6j5FK9uzRHEahP1IfQaKg80ENv8FE3pi4ga/
	 tjOKF5K8P3tDbV+lV1cOCBIT3L6/2vHQ8Z1kpuUg=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/110643] [13/14 Regression] aarch64: Miscompilation at O1
 level (O0 is working)
Date: Wed, 04 Oct 2023 16:14:47 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 13.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: MOVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.3
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-110643-4-Qun2jmbYji@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110643-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110643-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=3D110643

--- Comment #23 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note even though the optimization was in GCC 11+ (r11-2550-gca2b8c082c4f ad=
ded
it), only GCC 13+ hits it in this case as GCC 13 lowers the vector comparis=
on
and uses the scalar for the one element signed 64bit long. I have not looked
into which revision changed the behavior there though. But as I mentioned t=
his
is not a GCC bug really.=