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 4B6973884589; Thu,  6 Jun 2024 04:36:15 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4B6973884589
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1717648575;
	bh=tL1nMaORUf6WK4thZSw84OwHphjTOrxnj8QAZDYgMCc=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=jSKjEqqO6G2+PORyNVkODt5IadZDuhC77TnWnhUmGw5+3uV6uUeCVtvx2VHVVyCMl
	 EMGKwfVWOBMXv2Ucr0o5dnFUfRdXHlI9+ad+ci8TWTb067pm8ySmTJ6udBIAUUIPg/
	 8ppCy9DYOL8fXBywnDoKTHWEo0de8FJmmRZv1xCY=
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/115355] [12/13/14/15 Regression] vectorization exposes
 wrong code on P9 LE starting from r12-4496
Date: Thu, 06 Jun 2024 04:36:13 +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: 12.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: linkw at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 12.4
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-115355-4-5A6QPqPaw5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-115355-4@http.gcc.gnu.org/bugzilla/>
References: <bug-115355-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=3D115355

--- Comment #8 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #5)
> FYI, fails for me with gcc 12 and later and works with gcc 11.  It also
> fails with -O3 -mcpu=3Dpower10.

Thanks for the information, bisection shows r12-4496 is the culprit commit,=
 I
just tested and confirmed Xionghu's latest patch for PR106069 also fixed th=
is
one.

  - latest rev. for his fix:
https://inbox.sourceware.org/gcc-patches/20230210025952.1887696-1-xionghulu=
o@tencent.com/,
which was resent from
https://inbox.sourceware.org/gcc-patches/37b57a54-f98e-96a3-edff-866c8aae4c=
7d@gmail.com/

  - original thread and some discussions:
https://inbox.sourceware.org/gcc-patches/20220808034247.2618809-1-xionghulu=
o@tencent.com/

The latest rev. looked to me as
(https://inbox.sourceware.org/gcc-patches/e8e69f0c-7f36-e671-6c3b-74401e4d8=
c48@linux.ibm.com/),
still looking forward to Segher's review and approval on this.=