From: Joseph Myers <josmyers@redhat.com>
To: caiyinyu <caiyinyu@loongson.cn>
Cc: libc-alpha@sourceware.org, adhemerval.zanella@linaro.org,
xry111@xry111.site, xuchenghua@loongson.cn
Subject: Re: [PATCH] LoongArch: Add soft floating-point fe* function implementations.
Date: Tue, 2 Apr 2024 21:10:37 +0000 (UTC) [thread overview]
Message-ID: <5169739c-9483-41f0-d8e8-36b4fe8062aa@redhat.com> (raw)
In-Reply-To: <fe0e6a4f-d4ff-59dc-209c-3a5807f40640@loongson.cn>
[-- Attachment #1: Type: text/plain, Size: 1636 bytes --]
On Sun, 31 Mar 2024, caiyinyu wrote:
> LoongArch soft float support was added in version 2.37, but the fe* functions
> were not completely added. I want to backport this patch if possible
> (it requires some modifications) to the 2.37/38/39/master branch, so the
> version of
> the relevant symbols in Versions is GLIBC_2.37.
I don't think such new symbol additions are appropriate for backporting;
the GLIBC_2.37 symbol version contents should have been fixed at the time
2.37 was released.
> diff --git a/sysdeps/loongarch/nofpu/Versions
> b/sysdeps/loongarch/nofpu/Versions
> index 6d7f6aae6c..73b6a71bbd 100644
> --- a/sysdeps/loongarch/nofpu/Versions
> +++ b/sysdeps/loongarch/nofpu/Versions
> @@ -1,5 +1,13 @@
> libc {
> + GLIBC_2.37 {
> + __adddf3; __addsf3; __divdf3; __divsf3; __eqdf2; __eqsf2;
> + __extendsfdf2; __fixdfsi; __fixsfsi;
> + __fixunsdfsi; __fixunssfsi;
> + __floatsidf; __floatsisf;
> + __gedf2; __gesf2; __ledf2; __lesf2; __muldf3; __mulsf3;
> + __negdf2; __negsf2; __subdf3; __subsf3; __truncdfsf2;
> + }
I'd tend to expect you also to have the symbols that powerpc-nofpu has at
GLIBC_2.4 version.
__floatundidf; __floatundisf;
__floatunsidf; __floatunsisf;
__unorddf2; __unordsf2;
__nedf2; __nesf2;
__gtdf2; __gtsf2;
__ltdf2; __ltsf2;
Also, as LoongArch uses binary128 long double, I'd expect all the TFmode
symbols as well. And as a 64-bit architecture, I'd expect TImode symbols
(conversions between floating modes and 128-bit signed and unsigned
integers, in both directions) as well.
--
Joseph S. Myers
josmyers@redhat.com
next prev parent reply other threads:[~2024-04-02 21:10 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
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 [this message]
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=5169739c-9483-41f0-d8e8-36b4fe8062aa@redhat.com \
--to=josmyers@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=caiyinyu@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).