On 1/29/25 05:04, Peter Maydell wrote:
On Sat, 25 Jan 2025 at 16:42, Richard Henderson
wrote:
On 1/24/25 08:27, Peter Maydell wrote:
Currently we handle flushing of output denormals in uncanon_normal
always before we deal with rounding. This works for architectures
that detect tininess befor
On Sat, 25 Jan 2025 at 16:42, Richard Henderson
wrote:
>
> On 1/24/25 08:27, Peter Maydell wrote:
> > Currently we handle flushing of output denormals in uncanon_normal
> > always before we deal with rounding. This works for architectures
> > that detect tininess before rounding, but is usually n
On 1/27/25 02:01, Peter Maydell wrote:
On Sat, 25 Jan 2025 at 16:42, Richard Henderson
wrote:
On 1/24/25 08:27, Peter Maydell wrote:
Currently we handle flushing of output denormals in uncanon_normal
always before we deal with rounding. This works for architectures
that detect tininess befor
On Sat, 25 Jan 2025 at 16:42, Richard Henderson
wrote:
>
> On 1/24/25 08:27, Peter Maydell wrote:
> > Currently we handle flushing of output denormals in uncanon_normal
> > always before we deal with rounding. This works for architectures
> > that detect tininess before rounding, but is usually n
On 1/24/25 08:27, Peter Maydell wrote:
Currently we handle flushing of output denormals in uncanon_normal
always before we deal with rounding. This works for architectures
that detect tininess before rounding, but is usually not the right
place when the architecture detects tininess after roundi
