From: Florian Weimer <fweimer@redhat.com>
To: caiyinyu <caiyinyu@loongson.cn>
Cc: josmyers@redhat.com, libc-alpha@sourceware.org,
adhemerval.zanella@linaro.org, xry111@xry111.site
Subject: Re: [PATCH] LoongArch: Add soft floating-point fe* function implementations.
Date: Mon, 01 Apr 2024 15:19:13 +0200 [thread overview]
Message-ID: <87le5x1ar2.fsf@oldenburg3.str.redhat.com> (raw)
In-Reply-To: <20240331101400.474159-1-caiyinyu@loongson.cn> (caiyinyu@loongson.cn's message of "Sun, 31 Mar 2024 18:14:00 +0800")
> This patch accomplishes the following:
> 1. Implements soft floating-point functions to enhance compatibility and
> flexibility in environments without hardware floating-point support.
> 2. Refactors macro definitions by moving them from `fenv_libc.h` to
> `fpu_control.h`. This change not only simplifies the codebase but also
> eliminates the need for the unexported header file `fenv_libc.h`,
> streamlining the inclusion of floating-point utilities across different
> modules.
This patch appears to add a new ABI. The commit message doesn't mention
this, and it probably needs a NEWS update, too.
The new ABI is backdated to glibc 2.36. For new ABIs, we would expect a
glibc 2.40 baseline, but this is not a hard technical requirement.
Thanks,
Florian
next prev parent reply other threads:[~2024-04-01 13:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 12:46 caiyinyu
2024-03-26 17:34 ` Joseph Myers
2024-03-27 8:42 ` caiyinyu
2024-03-27 17:10 ` Joseph Myers
2024-03-31 10:14 ` caiyinyu
2024-04-01 13:19 ` Florian Weimer [this message]
2024-04-02 3:40 ` caiyinyu
2024-04-02 10:40 ` Xi Ruoyao
2024-04-02 11:45 ` Florian Weimer
2024-04-02 12:02 ` Xi Ruoyao
2024-04-02 12:34 ` Florian Weimer
2024-04-02 12:12 ` Andreas Schwab
2024-04-02 21:18 ` Joseph Myers
2024-03-31 10:31 ` caiyinyu
2024-04-02 21:10 ` Joseph Myers
2024-04-02 14:46 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=87le5x1ar2.fsf@oldenburg3.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=caiyinyu@loongson.cn \
--cc=josmyers@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=xry111@xry111.site \
/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).