From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D663B3898520; Thu, 30 Apr 2020 17:16:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D663B3898520 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1588266986; bh=FLn/EbuloSLovrXmWL/GxjshfV5f3ACQ+AzDGlmiQYc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=F8LVTtNG0KLqtGMIN7dPwal/s0hWEc6JkG24129M32vEVpt3GfovT/j+d0il2sk/t unOV7fjoGLIw2eMMGwnHt3OXWL8o1eaTBSLxYiu/PH4Cu4dzalMKRAQSqLpHHgdiOS Vn3Go+6IMmw3Blj7lZsEyX+r0YFzs6fu7ivJq7VM= From: "segher at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94687] PPC vector fails to optimize shift (used bits) Date: Thu, 30 Apr 2020 17:16:26 +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: 8.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: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_reconfirmed_on bug_status cc 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Apr 2020 17:16:26 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94687 Segher Boessenkool changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2020-04-30 Status|UNCONFIRMED |NEW CC| |segher at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Segher Boessenkool --- Confirmed. At combine time we start with insn_cost 4 for 25: r130:V1TI=3D%2:V1TI REG_DEAD %2:V1TI insn_cost 4 for 20: r129:V1TI=3Dr130:V1TI REG_DEAD r130:V1TI insn_cost 4 for 21: r127:DI=3Dr129:V1TI#0 insn_cost 4 for 22: r128:DI=3Dr129:V1TI#8 REG_DEAD r129:V1TI insn_cost 4 for 24: r123:TI=3D0 insn_cost 4 for 7: r123:TI#8=3Dr127:DI REG_DEAD r127:DI insn_cost 4 for 8: r123:TI#0=3Dr128:DI REG_DEAD r128:DI insn_cost 4 for 9: r122:V1TI=3Dr123:TI#0 REG_DEAD r123:TI insn_cost 4 for 14: %2:V1TI=3Dr122:V1TI REG_DEAD r122:V1TI insn_cost 0 for 15: use %2:V1TI and those subregs at the lhs (insns 7 and 8) cannot combine with anything. 2-to-2 combine won't handle 20+21 (and then, 20+22) because 20 is a register move already. It would probably combine fine if that subreg lhs problem was fixed though.=