public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thanm at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/67718] [aarch64] long double incorrect code for copysign
Date: Tue, 29 Sep 2015 15:17:00 -0000	[thread overview]
Message-ID: <bug-67718-4-z91CcWRpZ2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67718-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67718

--- Comment #2 from Than McIntosh <thanm at google dot com> ---

>>using __builtin_copysignl should generate better code generation anyways.

Tried replacing the guts of the function with a call to __builtin_copysignl --
the bug is still present.

Any recommendations on someone in the extended GCC community who could help me
triage/analyze the bug? I have worked with register allocators before, but not
with gcc's; I could use some guidance.


  parent reply	other threads:[~2015-09-29 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25 19:24 [Bug middle-end/67718] New: " thanm at google dot com
2015-09-25 23:31 ` [Bug target/67718] " pinskia at gcc dot gnu.org
2015-09-29 15:17 ` thanm at google dot com [this message]
2015-09-30  2:29 ` ramana at gcc dot gnu.org
2015-10-02 14:03 ` thanm at google dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-67718-4-z91CcWRpZ2@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).