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 A2AA13858C5F; Sun, 23 Jul 2023 21:05:34 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A2AA13858C5F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1690146334;
	bh=RiHg5XU4s3sGlaq5xv9/udpSy/kkowL+6frLdbO0gnU=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=tZF6jg30IW/kMANBslJwpSvZBAGUOEfXObw9ypXX42Kj/eh55225phQd/MPIYxS6+
	 X4568rCuE4p3Kq1ydknBSADgohElz+5VHlfNxOSnx0IYXfNbonoTPXG/O949eeijcg
	 f86hTgNQ4DchOiIp7YqBei7afri5z6N3zZRcuz6M=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110780] aarch64 NEON redundant displaced ld3
Date: Sun, 23 Jul 2023 21:05:34 +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: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
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: bug_severity component cf_reconfirmed_on
 bug_status everconfirmed
Message-ID: <bug-110780-4-7qxkWF45KR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110780-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110780-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=3D110780

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
          Component|target                      |tree-optimization
   Last reconfirmed|                            |2023-07-23
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The vectorizer produces:
  vectp_pBE.28_115 =3D (unsigned char[48] *) ivtmp.73_338;
  _218 =3D ivtmp.68_335 + 1;
  vectp_pCSI2.19_107 =3D (unsigned char[48] *) _218;
  vectp_pCSI2.10_98 =3D (unsigned char[48] *) ivtmp.68_335;
  vect_array.12 =3D .LOAD_LANES (MEM <unsigned char[48]> [(uint8_t
*)vectp_pCSI2.10_98]);
  vect__1.13_100 =3D vect_array.12[0];
  vect__1.14_101 =3D vect_array.12[1];
  vect__1.15_102 =3D vect_array.12[2];
  vect_array.12 =3D{v} {CLOBBER};
  vect__4.16_103 =3D vect__1.14_101 >> 4;
  vect__22.17_104 =3D vect__1.15_102 << 4;
  vect__5.18_105 =3D vect__4.16_103 | vect__22.17_104;
  vect_array.21 =3D .LOAD_LANES (MEM <unsigned char[48]> [(uint8_t
*)vectp_pCSI2.19_107]);
  vect__6.22_109 =3D vect_array.21[0];
  vect__6.23_110 =3D vect_array.21[1];
  vect_array.21 =3D{v} {CLOBBER};

Here vect__6.22_109 is the same as vect__1.14_101 and vect__6.23_110 is the
same as vect__1.15_102 (if I did this correctly).=