From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Xi Ruoyao <xry111@xry111.site>,
Xiaolin Tang <tangxiaolin@loongson.cn>,
libc-alpha@sourceware.org, caiyinyu@loongson.cn,
i.swmail@xen0n.name
Cc: xuchenghua@loongson.cn
Subject: Re: [PATCH 1/1] LoongArch: Hard Float Support Of Math Functions.
Date: Thu, 3 Nov 2022 13:14:59 -0300 [thread overview]
Message-ID: <4e93e1e9-95bd-ab51-cb15-bfbfd69cf09d@linaro.org> (raw)
In-Reply-To: <f2feefd02393e783a3dddf0ee24a4d977e9f3613.camel@xry111.site>
On 03/11/22 11:39, Xi Ruoyao wrote:
> On Thu, 2022-11-03 at 09:42 -0300, Adhemerval Zanella Netto via Libc-alpha wrote:
>> On 03/11/22 09:14, Xiaolin Tang wrote:
>
>>> fcopysign.{s/d __copysign{f/ }
>>
>> GCC already implements a generic builtin copysign that expands it without a
>> libcall, I prefer to implement it on compiler (which I presume it will be on
>> 13, since on gcc 12 I do see fcopysign.d). I will send a patch to remove
>> the RISCV version as well.
>
> GCC trunk still generates some nasty thing for __builtin_copysign yet:
>
> movfr2gr.d $r12,$f1
> fabs.d $f0,$f0
> bge $r12,$r0,.L1
> fneg.d $f0,$f0
> .L1:
> jr $r1
>
> Fortunately we still have ten days before GCC 13 stage 1 ends. I'll try
> to fix it...
>
Yes, this is most likely the generic lowering.
prev parent reply other threads:[~2022-11-03 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 12:14 [PATCH 0/1] " Xiaolin Tang
2022-11-03 12:14 ` [PATCH 1/1] " Xiaolin Tang
2022-11-03 12:42 ` Adhemerval Zanella Netto
2022-11-03 14:39 ` Xi Ruoyao
2022-11-03 16:14 ` Adhemerval Zanella Netto [this message]
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=4e93e1e9-95bd-ab51-cb15-bfbfd69cf09d@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=caiyinyu@loongson.cn \
--cc=i.swmail@xen0n.name \
--cc=libc-alpha@sourceware.org \
--cc=tangxiaolin@loongson.cn \
--cc=xry111@xry111.site \
--cc=xuchenghua@loongson.cn \
/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).