son' ; qemu-devel@nongnu.org
Subject: RE: Denormal input handling
Richard,
I was under the mistaken impression that your changes in this area (splitting
float_flag_input_denormal into 2 flags) were already checked in, but I see now
that is not the case. I should probably wait until
.
Michael
-Original Message-
From: Richard Henderson
Sent: Monday, June 21, 2021 4:30 PM
To: Michael Morrell ; qemu-devel@nongnu.org
Subject: Re: Denormal input handling
On 6/21/21 4:13 PM, Michael Morrell wrote:
> I have another couple of thoughts around input denormal handling.
>
, June 21, 2021 4:30 PM
To: Michael Morrell ; qemu-devel@nongnu.org
Subject: Re: Denormal input handling
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'
upport 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 idi
like IXC, but
nothing for IDC. Is that simply because no one has bothered to add this
support?
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
On 5/26/21 2:59 PM, Michael Morrell wrote:
First, I apologize for the duplicate thread. I thought the first attempt
didn't go through.
I agree with Richard that we need an extra flag bit. The current behavior is
not right for SSE on x86 (it looks like x87 might be different still). For
AR
.
Richard, are you willing to make the change or do you want me to try?
Thanks,
Michael
-Original Message-
From: Peter Maydell
Sent: Wednesday, May 26, 2021 1:19 PM
To: Michael Morrell
Cc: qemu-devel@nongnu.org; Richard Henderson
Subject: Re: Denormal input handling
On Wed, 26 May
So, DE should not be set for a denormal input if DAZ is set (it is set only
when DAZ is 0 -- the default "IEEE mode").
It's not my day is it? Clearly the bit that I quoted is wrt to the output
denormal flushing. But my suggested fix is still not wrong -- have two bits
that cover both alterna
On Wed, 26 May 2021 at 20:07, Michael Morrell wrote:
> I see support in QEMU for architectures which have a denormal
> input flag bit and those that have a "flush inputs to zero" control
> bit, but the implementation is not specializable and seems wrong
> for x86 at least.
> For example, in sf_ca
Richard,
How is what I suggested wrong for x86? It matches the spec and actual behavior:
== Start quote ==
10.2.3.4 Denormals-Are-Zeros
Bit 6 (DAZ) of the MXCSR register enables the denormals-are-zeros mode, which
controls the processor’s response
to a SIMD floating-point denormal operand con
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
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
I see support in QEMU for architectures which have a denormal input flag bit
and those that have a "flush inputs to zero" control bit, but the
implementation is not specializable and seems wrong for x86 at least.
For example, in sf_canonicalize, if the input is denormal and
"flush_inputs_to_zer
I see support in QEMU for architectures which have a denormal input flag bit
and those that have a "flush inputs to zero" control bit, but the
implementation is not specializable and seems wrong for x86 at least.
For example, in sf_canonicalize, if the input is denormal and
"flush_inputs_to_zer
14 matches
Mail list logo