From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28011 invoked by alias); 30 Sep 2015 02:29:02 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 27976 invoked by uid 48); 30 Sep 2015 02:28:58 -0000 From: "ramana at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/67718] [aarch64] long double incorrect code for copysign Date: Wed, 30 Sep 2015 02:29:00 -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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ramana at gcc dot gnu.org X-Bugzilla-Status: WAITING 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: bug_status cf_reconfirmed_on cc everconfirmed Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-09/txt/msg02344.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67718 Ramana Radhakrishnan changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2015-09-30 CC| |ramana at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #3 from Ramana Radhakrishnan --- With the latest build for aarch64-none-linux-gnu of 4.9 and trunk that I had lying around, I see with -O2 and with and without a variety of tuning options, which looks a whole load better than the original bug report. copysignl: fmov x2, d0 fmov x1, v1.d[1] fmov x3, v0.d[1] fmov d0, x2 lsr x1, x1, 63 bfi x3, x1, 63, 1 fmov v0.d[1], x3 ret .size copysignl, .-copysignl .ident "GCC: 4.9.4 20150924 (prerelease)" I am traveling currently and can't dig any further but I remember something being fixed in this pattern with respect to early clobbers- Aha PR61633 may be your friend. Can you check if you have the fix for PR61633 in your 4.9 based tree ? In the future please report with command line options and the exact upstream source revision used to create the issue. regards Ramana