From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id DF9873858C54; Tue, 28 Feb 2023 16:57:49 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DF9873858C54 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1677603469; bh=f+kHtHl7j9ZYy5v4B8HQ+Ck5rWoPhSUF401SgOV+sko=; h=From:To:Subject:Date:In-Reply-To:References:From; b=JPN2SFjx9mGgwybQVbGfLo0O/pRyeH1IHA7efCyR/MHexnle4LG24MPSKMIaS2R0E y4q3UowaAj269SzZF7cJr1/ZmsEc4RQK3UjKLJOWQFWJogP5SQOqryZPpjnpVjVJ7R ZNDiUa4Zn0QzQWb/OGGEz8qLVvhPRnUrHYEWLD7o= From: "segher at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106770] PPCLE: Unnecessary xxpermdi before mfvsrd Date: Tue, 28 Feb 2023 16:57:45 +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: 11.2.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: segher at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jskumari at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_gcctarget cf_reconfirmed_on everconfirmed 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=3D106770 Segher Boessenkool changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Target|powerpc |powerpc64le Last reconfirmed| |2023-02-28 Ever confirmed|0 |1 --- Comment #7 from Segher Boessenkool --- The mystery is not where the permutations came from: they were added during expand to make correct code, just like many unnecessary register moves are added at that time. This is normal, and even good in many ways. The question is why they weren't optimised better. This is either due to some bug, or this is an enhancement request.=