From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3A9DD385F01B; Fri, 20 Mar 2020 14:13:14 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3A9DD385F01B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1584713594; bh=CIst+FtS1bJF2v8PhAFYXOv6N4aQRd4NlFpUX5SLe14=; h=From:To:Subject:Date:In-Reply-To:References:From; b=vNuEAxuJt8mMJE1W7X/wuLVhAVQrERl3hhGMePl8/Y2jJ/mlnw0bhyttTFvywv1Cz Op3E7pf4Ed80mfFWxU59DtAkOESMRKJjb9sBS42rP6uk/6ee9GAjMSZrpwpDehSaS+ zkjsOK6RHX8yxiG5B7EhsXYK2AmgLS8qkLlgPLWQ= From: "bergner at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94123] [10 regression] r10-1734, SVN r273240, causes gcc.target/powerpc/pr87507.c to fail Date: Fri, 20 Mar 2020 14:13: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: 10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: bergner at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: Fri, 20 Mar 2020 14:13:14 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94123 Peter Bergner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu.org --- Comment #6 from Peter Bergner --- (In reply to Segher Boessenkool from comment #5) > Confirmed. >=20 > On p9 it is all fine. >=20 > On p7 it is worse, you get std's followed by an lxvd2x from the same stack > address (big LHS/SHL hazard there), and then two stxvd2x. >=20 > On p8 the TImode values aren't split at all, not until final output anywa= y. My fix for PR87507 allowed them to be split early so they could be optimize= d, so this must have regressed without us seeing it. I'll have a quick look at what is happening. Richi, given this is a performance issue for TImode values, is there a reas= on you want this as a P1 bug?=