From: Xi Ruoyao <xry111@xry111.site>
To: Florian Weimer <fweimer@redhat.com>
Cc: caiyinyu <caiyinyu@loongson.cn>,
josmyers@redhat.com, libc-alpha@sourceware.org,
adhemerval.zanella@linaro.org
Subject: Re: [PATCH] LoongArch: Add soft floating-point fe* function implementations.
Date: Tue, 02 Apr 2024 20:02:53 +0800 [thread overview]
Message-ID: <5e713d506244070b9ba6e8bd0cd4dc32648bb6ce.camel@xry111.site> (raw)
In-Reply-To: <87y19wxa2a.fsf@oldenburg3.str.redhat.com>
On Tue, 2024-04-02 at 13:45 +0200, Florian Weimer wrote:
> > Or maybe we can provide both feenableexcept@GLIBC_2_37 and
> > feenableexcept@GLIBC_2_40 in libm.so.6? I don't know if doing so is
> > really possible.
>
> Yes, it's possible to add a compat symbol for that and keep the
> do-nothing behavior for old applications.
>
> Wouldn't the issue manifest on other architectures with a working
> (non-stub) feenableexcept implementation?
Has there been another port where the fe* implementation was changed
from stub to real? Then I'd say just do what that port did.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2024-04-02 12:02 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 [this message]
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=5e713d506244070b9ba6e8bd0cd4dc32648bb6ce.camel@xry111.site \
--to=xry111@xry111.site \
--cc=adhemerval.zanella@linaro.org \
--cc=caiyinyu@loongson.cn \
--cc=fweimer@redhat.com \
--cc=josmyers@redhat.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).