From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Thomas Bogendoerfer" <tsbogend@alpha.franken.de>
Cc: "Maciej W. Rozycki" <macro@orcam.me.uk>,
"Jonathan Corbet" <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v3] MIPS: Implement ieee754 NAN2008 emulation mode
Date: Wed, 10 Jul 2024 16:16:35 +0800 [thread overview]
Message-ID: <daf23c57-9058-479c-aab1-c9d9d172edc0@app.fastmail.com> (raw)
In-Reply-To: <Zo457UgAkhbAgm2R@alpha.franken.de>
在2024年7月10日七月 下午3:36，Thomas Bogendoerfer写道：
[...]
>> It has been tested against Debian rootfs. There is no need to test againt special binary,
>> but you need NaN2008 hardware such as Loongson 3A4000.
>
> that's just one case, what about NaN2008 binaries on a legacy MIPS CPU ?
Never checked that, as we don't have any NaN2008 distro.
Will try and report.
>
> Thomas.
>
> --
> Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
> good idea. [ RFC1925, 2.3 ]
--
- Jiaxun
next prev parent reply other threads:[~2024-07-10 8:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 8:38 [PATCH v3] MIPS: Implement ieee754 NAN2008 emulation mode Jiaxun Yang
2024-06-27 10:58 ` Thomas Bogendoerfer
2024-06-27 11:21 ` Jiaxun Yang
2024-06-27 19:54 ` Maciej W. Rozycki
2024-06-28 0:33 ` Jiaxun Yang
2024-07-09 8:55 ` Thomas Bogendoerfer
2024-07-10 5:34 ` Jiaxun Yang
2024-07-10 7:36 ` Thomas Bogendoerfer
2024-07-10 8:16 ` Jiaxun Yang [this message]
2024-07-10 9:21 ` Maciej W. Rozycki
2024-07-11 1:53 ` Jiaxun Yang
2024-07-11 10:20 ` Maciej W. Rozycki
2024-07-12 0:36 ` Jiaxun Yang
2024-07-12 12:22 ` Maciej W. Rozycki
2024-07-14 3:11 ` Jiaxun Yang
2024-07-15 12:15 ` Maciej W. Rozycki
2024-07-15 12:35 ` Jiaxun Yang
2024-07-15 14:01 ` Maciej W. Rozycki
2024-07-15 16:38 ` YunQiang Su
2024-08-22 8:02 ` Thomas Bogendoerfer
2024-08-22 9:20 ` Jiaxun Yang
2024-07-11 1:47 ` Jiaxun Yang
2024-07-12 11:21 ` Thomas Bogendoerfer
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=daf23c57-9058-479c-aab1-c9d9d172edc0@app.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=philmd@linaro.org \
--cc=tsbogend@alpha.franken.de \
/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 NNTP newsgroup(s).