From: tangxiaolin <tangxiaolin@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, gcc-patches@gcc.gnu.org
Cc: Lulu Cheng <chenglulu@loongson.cn>, Wang Xuerui <i@xen0n.name>,
Chenghua Xu <xuchenghua@loongson.cn>,
caiyinyu@loongson.cn
Subject: Re: [PATCH v2 0/4] LoongArch: Add some floating-point operations
Date: Mon, 14 Nov 2022 10:41:45 +0800 [thread overview]
Message-ID: <235d9f8e-040c-2917-8444-654b33aa124e@loongson.cn> (raw)
In-Reply-To: <1a465d2a0bea2a47aadaa727c0689ac48d5982c5.camel@xry111.site>
How about I do this work on Glibc?
在 2022/11/12 下午3:08, Xi Ruoyao 写道:
> On Wed, 2022-11-09 at 21:53 +0800, Xi Ruoyao wrote:
>> These patches allow to expand the following builtins to floating point
>> instructions for LoongArch:
>>
>> - __builtin_rint{,f}
>> - __builtin_{l,ll}rint{,f}
>> - __builtin_{l,ll}floor{,f}
>> - __builtin_{l,ll}ceil{,f}
>> - __builtin_scalb{n,ln}{,f}
>> - __builtin_logb{,f}
>>
>> Bootstrapped and regtested on loongarch64-linux-gnu. And a modified
>> Glibc using the builtins for rint{,f}, {l,ll}rint{,f}, and logb{,f}
>> also survived Glibc test suite.
>>
>> Please review ASAP because GCC 13 stage 1 will end on Nov. 13th.
>>
>> v1 -> v2: Only use ftint{rm,rp} instructions if floor and ceil are
>> allowed to raise inexact exception.
>>
>> Xi Ruoyao (4):
>> LoongArch: Rename frint_<fmt> to rint<mode>2
>> LoongArch: Add ftint{,rm,rp}.{w,l}.{s,d} instructions
>> LoongArch: Add fscaleb.{s,d} instructions as ldexp{sf,df}3
>> LoongArch: Add flogb.{s,d} instructions and expand logb{sf,df}2
>>
>> gcc/config/loongarch/loongarch.md | 95
>> ++++++++++++++++++-
>> gcc/testsuite/gcc.target/loongarch/flogb.c | 18 ++++
>> gcc/testsuite/gcc.target/loongarch/frint.c | 16 ++++
>> gcc/testsuite/gcc.target/loongarch/fscaleb.c | 48 ++++++++++
>> .../gcc.target/loongarch/ftint-no-inexact.c | 44 +++++++++
>> gcc/testsuite/gcc.target/loongarch/ftint.c | 44 +++++++++
>> 6 files changed, 261 insertions(+), 4 deletions(-)
>> create mode 100644 gcc/testsuite/gcc.target/loongarch/flogb.c
>> create mode 100644 gcc/testsuite/gcc.target/loongarch/frint.c
>> create mode 100644 gcc/testsuite/gcc.target/loongarch/fscaleb.c
>> create mode 100644 gcc/testsuite/gcc.target/loongarch/ftint-no-
>> inexact.c
>> create mode 100644 gcc/testsuite/gcc.target/loongarch/ftint.c
>>
> Pushed r13-3922.
>
> I'll be busy in the following week. Will do the work on Glibc side
> after Nov. 20.
>
prev parent reply other threads:[~2022-11-14 2:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 13:53 Xi Ruoyao
2022-11-09 13:53 ` [PATCH v2 1/4] LoongArch: Rename frint_<fmt> to rint<mode>2 Xi Ruoyao
2022-11-10 8:15 ` Lulu Cheng
2022-11-09 13:53 ` [PATCH v2 2/4] LoongArch: Add ftint{,rm,rp}.{w,l}.{s,d} instructions Xi Ruoyao
2022-11-10 6:41 ` Lulu Cheng
2022-11-10 8:49 ` Xi Ruoyao
2022-11-11 0:07 ` Joseph Myers
2022-11-11 5:29 ` Xi Ruoyao
2022-11-12 1:58 ` Lulu Cheng
2022-11-09 13:53 ` [PATCH v2 3/4] LoongArch: Add fscaleb.{s,d} instructions as ldexp{sf,df}3 Xi Ruoyao
2022-11-12 3:54 ` Lulu Cheng
2022-11-12 4:40 ` Xi Ruoyao
2022-11-12 6:52 ` Lulu Cheng
2022-11-09 13:53 ` [PATCH v2 4/4] LoongArch: Add flogb.{s,d} instructions and expand logb{sf,df}2 Xi Ruoyao
2022-11-12 6:51 ` Lulu Cheng
2022-11-12 7:08 ` [PATCH v2 0/4] LoongArch: Add some floating-point operations Xi Ruoyao
2022-11-12 7:14 ` Lulu Cheng
2022-11-14 2:41 ` tangxiaolin [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=235d9f8e-040c-2917-8444-654b33aa124e@loongson.cn \
--to=tangxiaolin@loongson.cn \
--cc=caiyinyu@loongson.cn \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--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).