From: Xi Ruoyao <xry111@xry111.site>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
Cc: caiyinyu <caiyinyu@loongson.cn>,
Joseph Myers <joseph@codesourcery.com>,
Wang Xuerui <i.swmail@xen0n.name>
Subject: Re: [PATCH] LoongArch: Use __builtin_{fmax,fmaxf,fmin,fminf} with GCC >= 13
Date: Tue, 30 Aug 2022 13:31:57 +0800 [thread overview]
Message-ID: <7eba37096433a9030a4587fe80ad683f79432a32.camel@xry111.site> (raw)
In-Reply-To: <532ed62c-8510-c351-9cf2-342771a09a94@linaro.org>
On Mon, 2022-08-29 at 09:44 -0300, Adhemerval Zanella Netto wrote:
>
>
> On 20/08/22 05:43, Xi Ruoyao wrote:
> > GCC 13 compiles these built-ins to {fmax,fmin}.{s/d} instruction, use
> > them instead of the generic implementation.
> >
> > Link: https://gcc.gnu.org/r13-2085
> > Signed-off-by: Xi Ruoyao <xry111@xry111.site>
>
> LGTM, thanks.
>
> Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Thanks, I don't have a write access to glibc.git and need others' help
to push the patch :).
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-08-30 5:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 8:43 Xi Ruoyao
2022-08-29 7:11 ` Ping: " Xi Ruoyao
2022-08-29 12:44 ` Adhemerval Zanella Netto
2022-08-29 12:44 ` [PATCH] LoongArch: Use __builtin_{fmax, fmaxf, fmin, fminf} " Adhemerval Zanella Netto
2022-08-30 5:31 ` Xi Ruoyao [this message]
2022-08-30 6:23 ` [PATCH] LoongArch: Use __builtin_{fmax,fmaxf,fmin,fminf} " caiyinyu
2022-08-30 6:23 ` [PATCH] LoongArch: Use __builtin_{fmax, fmaxf, fmin, fminf} " caiyinyu
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=7eba37096433a9030a4587fe80ad683f79432a32.camel@xry111.site \
--to=xry111@xry111.site \
--cc=adhemerval.zanella@linaro.org \
--cc=caiyinyu@loongson.cn \
--cc=i.swmail@xen0n.name \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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).