From: Richard Henderson <richard.henderson@linaro.org>
To: morrell@alumni.ucsd.edu, qemu-devel@nongnu.org
Subject: Re: Denormal input handling
Date: Wed, 26 May 2021 12:28:34 -0700 [thread overview]
Message-ID: <b6cc921d-afad-9b39-e13a-9789bd873f99@linaro.org> (raw)
In-Reply-To: <4bc4444e-782a-311c-719d-091a04e20387@linaro.org>
On 5/26/21 12:23 PM, Richard Henderson wrote:
> On 5/26/21 12:02 PM, Michael Morrell via wrote:
>> I think the behavior should be for denormal inputs that if
>> "flush_inputs_to_zero" is true, then set the value to zero (without setting
>> the "input denormal" flag); and if "flush_inputs_to_zero" is false, set the
>> "input denormal" flag and normalize the input.
>>
>> This matches what x86 does (I'm not sure about other architectures).
>
> It is not.
>
> Intel Architectures SDM Vol 1, Section 11.5.2.2:
> The denormal operand exception is not affected by
> flush-to-zero mode.
Ho hum, I misread what you wrote outside the quoted context.
Both your suggestion and the current behaviour are wrong for x86. The current
behavior is correct for arm.
What we need are two separate softfloat flags, one for "any denormal seen on
input" and another for "denormal flushed to zero on input".
The target emulation code then chooses what set of bits needs exporting to
target architecture state.
r~
next prev parent reply other threads:[~2021-05-26 19:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <746277332.296230.1622055775751.ref@mail.yahoo.com>
2021-05-26 19:02 ` Denormal input handling Michael Morrell via
2021-05-26 19:23 ` Richard Henderson
2021-05-26 19:28 ` Richard Henderson [this message]
2021-05-26 19:52 ` Michael Morrell via
2021-05-26 20:15 ` Richard Henderson
2021-05-26 17:37 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
2021-06-21 23:39 ` Michael Morrell
2021-06-22 0:57 ` Michael Morrell
2021-06-22 18:50 ` Michael Morrell
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=b6cc921d-afad-9b39-e13a-9789bd873f99@linaro.org \
--to=richard.henderson@linaro.org \
--cc=morrell@alumni.ucsd.edu \
--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).