From: tangxiaolin <tangxiaolin@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>,
adhemerval.zanella@linaro.org, libc-alpha@sourceware.org,
caiyinyu@loongson.cn
Cc: xuchenghua@loongson.cn, chenglulu@loongson.cn
Subject: Re: [PATCH 0/9] LoongArch: Use builtins with GCC >= 13
Date: Wed, 23 Nov 2022 10:14:41 +0800 [thread overview]
Message-ID: <ea22b56f-54e7-43f2-3b34-67c53e98c799@loongson.cn> (raw)
In-Reply-To: <16d2603ead227edc39cd46bbd25c0fb4611c0392.camel@xry111.site>
OK, thank you for pointing this out. Please delete them, and I will
resend this series.
在 2022/11/23 上午12:20, Xi Ruoyao 写道:
> Hi Xiaolin,
>
> I guess you need to resent the series because {1,8,9}/9 lacks the proper
> In-Reply-To: header, causing them missing from the patchwork interface
> (https://patchwork.sourceware.org/project/glibc/list/?series=14494).
> The reviewers will use the patchwork interface to track the patches.
>
> On Fri, 2022-11-18 at 19:29 +0800, Xiaolin Tang wrote:
>> Patch 0001-0007:
>> GCC 13, LoongArch support builtins for {,l,ll}rint, logb,
>> use these built-ins instead of generic function implementation.
>>
>> Patch 0008:
>> GCC 13, LoongArch support ___builtin_scalbn{,f} with -fno-math-errno,
>> but only "libm" can use -fno-math-errno in GLIBC, and scalbn is in
>> libc
>> instead of libm because __printf_fp calls it. So inline assembler of
>> the scalbn functions is a better choice for LoongArch.
>>
>> Patch 0009: Add LoongArch support for scalb[f].
>>
>> Discuss with Xi Ruoyao<xry111@xry111.site>
>> Link:
>> https://sourceware.org/pipermail/libc-alpha/2022-November/143425.html
>>
>> Xi Ruoyao (1):
>> LoongArch: Use __builtin_rint{,f} with GCC >= 13
>>
>> Xiaolin Tang (8):
>> Use GCC builtins for lrint functions if desired.
>> LoongArch: Use __builtin_lrint{,f} with GCC >= 13
>> Use GCC builtins for llrint functions if desired.
>> LoongArch: Use __builtin_llrint{,f} with GCC >= 13
>> Use GCC builtins for logb functions if desired.
>> LoongArch: Use __builtin_logb{,f} with GCC >= 13
>> LoongArch: Add support for scalbn[f]
>> LoongArch: Add support for scalb[f]
>>
>> sysdeps/generic/math-use-builtins-llrint.h | 4 ++
>> sysdeps/generic/math-use-builtins-logb.h | 4 ++
>> sysdeps/generic/math-use-builtins-lrint.h | 4 ++
>> sysdeps/generic/math-use-builtins.h | 3 +
>> sysdeps/ieee754/dbl-64/s_llrint.c | 18 ++++--
>> sysdeps/ieee754/dbl-64/s_logb.c | 5 ++
>> sysdeps/ieee754/dbl-64/s_lrint.c | 18 ++++--
>> sysdeps/ieee754/float128/float128_private.h | 6 ++
>> sysdeps/ieee754/flt-32/s_llrintf.c | 18 ++++--
>> sysdeps/ieee754/flt-32/s_logbf.c | 5 ++
>> sysdeps/ieee754/flt-32/s_lrintf.c | 18 ++++--
>> sysdeps/ieee754/ldbl-128/s_llrintl.c | 17 ++++--
>> sysdeps/ieee754/ldbl-128/s_logbl.c | 6 ++
>> sysdeps/ieee754/ldbl-128/s_lrintl.c | 17 ++++--
>> sysdeps/loongarch/fpu/e_scalb.c | 60
>> +++++++++++++++++++
>> sysdeps/loongarch/fpu/e_scalbf.c | 60
>> +++++++++++++++++++
>> .../loongarch/fpu/math-use-builtins-llrint.h | 10 ++++
>> .../loongarch/fpu/math-use-builtins-logb.h | 10 ++++
>> .../loongarch/fpu/math-use-builtins-lrint.h | 10 ++++
>> .../loongarch/fpu/math-use-builtins-rint.h | 9 +++
>> sysdeps/loongarch/fpu/s_scalbn.c | 29 +++++++++
>> sysdeps/loongarch/fpu/s_scalbnf.c | 29 +++++++++
>> 22 files changed, 326 insertions(+), 34 deletions(-)
>> create mode 100644 sysdeps/generic/math-use-builtins-llrint.h
>> create mode 100644 sysdeps/generic/math-use-builtins-logb.h
>> create mode 100644 sysdeps/generic/math-use-builtins-lrint.h
>> create mode 100644 sysdeps/loongarch/fpu/e_scalb.c
>> create mode 100644 sysdeps/loongarch/fpu/e_scalbf.c
>> create mode 100644 sysdeps/loongarch/fpu/math-use-builtins-llrint.h
>> create mode 100644 sysdeps/loongarch/fpu/math-use-builtins-logb.h
>> create mode 100644 sysdeps/loongarch/fpu/math-use-builtins-lrint.h
>> create mode 100644 sysdeps/loongarch/fpu/math-use-builtins-rint.h
>> create mode 100644 sysdeps/loongarch/fpu/s_scalbn.c
>> create mode 100644 sysdeps/loongarch/fpu/s_scalbnf.c
>>
next prev parent reply other threads:[~2022-11-23 2:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 11:29 Xiaolin Tang
2022-11-18 11:29 ` [PATCH 1/9] LoongArch: Use __builtin_rint{,f} " Xiaolin Tang
2022-11-18 11:29 ` [PATCH 2/9] Use GCC builtins for lrint functions if desired Xiaolin Tang
2022-11-18 11:29 ` [PATCH 3/9] LoongArch: Use __builtin_lrint{,f} with GCC >= 13 Xiaolin Tang
2022-11-18 11:29 ` [PATCH 4/9] Use GCC builtins for llrint functions if desired Xiaolin Tang
2022-11-18 11:29 ` [PATCH 5/9] LoongArch: Use __builtin_llrint{,f} with GCC >= 13 Xiaolin Tang
2022-11-18 11:29 ` [PATCH 6/9] Use GCC builtins for logb functions if desired Xiaolin Tang
2022-11-18 11:29 ` [PATCH 7/9] LoongArch: Use __builtin_logb{,f} with GCC >= 13 Xiaolin Tang
2022-11-22 16:20 ` [PATCH 0/9] LoongArch: Use builtins " Xi Ruoyao
2022-11-23 2:14 ` tangxiaolin [this message]
2022-11-23 2:55 ` tangxiaolin
2022-11-23 3:18 ` Xi Ruoyao
2022-11-23 2:38 Xiaolin Tang
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=ea22b56f-54e7-43f2-3b34-67c53e98c799@loongson.cn \
--to=tangxiaolin@loongson.cn \
--cc=adhemerval.zanella@linaro.org \
--cc=caiyinyu@loongson.cn \
--cc=chenglulu@loongson.cn \
--cc=libc-alpha@sourceware.org \
--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).