From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 43554385B529; Wed, 12 Jun 2024 02:39:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 43554385B529 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1718159966; bh=IkSk8qH1RQg3/OHfDtY3NDtokI+eDCNNRBkPNTVrZr8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=xlJSLHV05bED5MdoSax1IH8wFT1dEK56YyhN9/YuHVus38uO/iZTWJLRP0yT70uvQ 4dT7Y2BEhC4aas3CO81nQKDt2p5h1b66xNJQWVrFW9LNbPvCJNoCa0Jn7YD6IoAsZT B2biwYF5zdQDncu4rwK1WDm5FkLr1NNrPDSLPVyE= From: "linkw at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/115262] [15 regression] gcc.target/powerpc/pr66144-3.c fails after r15-831-g05daf617ea22e1 Date: Wed, 12 Jun 2024 02:39:25 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 15.0 X-Bugzilla-Keywords: testsuite-fail X-Bugzilla-Severity: normal X-Bugzilla-Who: linkw 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: 15.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D115262 --- Comment #3 from Kewen Lin --- (In reply to Peter Bergner from comment #2) > (In reply to Jeffrey A. Law from comment #1) > > It looks like the test wants to see xxsel, but after that change we get > > xxlor and what looks like a slight difference in register allocation. = I > > can't really judge if the new code is better, worse is equivalent. >=20 > xxsel XT,XA,XB,XC computes XT =3D (XA & ~XC) | (XB & XC). Using De Morga= n's > law given XB =3D=3D XC, that seems to simplify to XT =3D XA | XB which is= what > you're producing and an xxlor (a simple logical or) is not going to be > slower than a xxsel and is probably faster. I agree with Bill that this > looks like an example of needing to update the expected results of the te= st > case. I'll let Segher and/or Ke Wen comment though. I agree they are equivalent here, from the scheduling descriptions, xxsel a= nd xxlor are in the same unit.=