From: Richard Henderson <richard.henderson@linaro.org>
To: Michael Morrell <mmorrell@tachyum.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: Denormal input handling
Date: Mon, 21 Jun 2021 16:30:26 -0700 [thread overview]
Message-ID: <08ba29ee-d5c0-8c61-0efc-4c03fe9da944@linaro.org> (raw)
In-Reply-To: <c021f386dcfb49aca2ab0c01f66bccc2@tachyum.com>
On 6/21/21 4:13 PM, Michael Morrell wrote:
> I have another couple of thoughts around input denormal handling.
>
> The first is straightforward. I noticed that the Aarch64 port doesn't report input
> denormals (I could not find any code which sets the IDC bit in the FPSR). I found code in
> the arm (not aarch64) port that sets other bits like IXC, but nothing for IDC. Is that
> simply because no one has bothered to add this support?
It's because we failed to use symbolic constants. See vfp_exceptbits_from_host. Which
*is* used for both aarch64 and arm.
> The second concerns support for cases where multiple exception conditions occur. I had
> originally thought that denormal input handling would be orthogonal to everything else and
> so a case like "sNaN + denorm" would set both the invalid and input denormal flags or
> "denorm / 0" would set both idivde by zero and input denormal, but I don't think that is
> true for at least some architectures. Perhaps some specialization is needed here?
If you've got a specific example, we can look at it. There's no point adding
specialization that isn't going to be used.
r~
next prev parent reply other threads:[~2021-06-21 23:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 17:37 Denormal input handling Michael Morrell
2021-05-26 20:18 ` Peter Maydell
2021-05-26 21:59 ` Michael Morrell
2021-05-27 1:14 ` Richard Henderson
2021-06-21 23:13 ` Michael Morrell
2021-06-21 23:30 ` Richard Henderson [this message]
2021-06-21 23:39 ` Michael Morrell
2021-06-22 0:57 ` Michael Morrell
2021-06-22 18:50 ` Michael Morrell
[not found] <746277332.296230.1622055775751.ref@mail.yahoo.com>
2021-05-26 19:02 ` Michael Morrell via
2021-05-26 19:23 ` Richard Henderson
2021-05-26 19:28 ` Richard Henderson
2021-05-26 19:52 ` Michael Morrell via
2021-05-26 20:15 ` Richard Henderson
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=08ba29ee-d5c0-8c61-0efc-4c03fe9da944@linaro.org \
--to=richard.henderson@linaro.org \
--cc=mmorrell@tachyum.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).