On Mon, 20 Jun 2016, Aleksandar Markovic wrote:
> This patch is about NaN-2008 flavor of Mips instructions CEIL, CVT,
> FLOOR, ROUND, TRUNC only (its title is "Add nan2008 flavor...").
>
> Legacy-NaN flavors of the same Mips instructions already operate
> correctly, and there is nothing to be f
This patch is about NaN-2008 flavor of Mips instructions CEIL, CVT, FLOOR,
ROUND, TRUNC only (its title is "Add nan2008 flavor...").
Legacy-NaN flavors of the same Mips instructions already operate correctly, and
there is nothing to be fixed.
The commit message is not description of another bug
On Tue, 14 Jun 2016, Leon Alrae wrote:
> > 1. A bug fix for SoftFloat legacy-NaN (original) MIPS support, which has
> >been there probably since forever (i.e. since the MIPS target was added
> >to QEMU).
>
> I've just done another round of review and as far as I can tell these
> patches
On Fri, Jun 10, 2016 at 09:12:12PM +0100, Maciej W. Rozycki wrote:
> On Fri, 10 Jun 2016, Aleksandar Markovic wrote:
>
> > The changes that make QEMU behavior the same as hardware behavior (in
> > relation to CEIL, CVT, FLOOR, ROUND, TRUNC Mips instructions) are
> > already contained in this pat
On Fri, 10 Jun 2016, Aleksandar Markovic wrote:
> The changes that make QEMU behavior the same as hardware behavior (in
> relation to CEIL, CVT, FLOOR, ROUND, TRUNC Mips instructions) are
> already contained in this patch.
Good, however that means that you've really combined two logically
sep
The changes that make QEMU behavior the same as hardware behavior (in relation
to CEIL, CVT, FLOOR, ROUND, TRUNC Mips instructions) are already contained in
this patch.
I just mentioned Mips-A / Mips-B / SoftFloat differences as an
explanation/observation related to the change in this patch.
A
On Fri, 10 Jun 2016, Aleksandar Markovic wrote:
> I referred to SoftFloat library in QEMU code, and the case "Operand is
> smaller than INT_MIN" is different between SoftFloat and Mips-B, while
> the case "Operand is a NaN" is different between SoftFloat and Mips-A.
Ah, but then you just can a
I referred to SoftFloat library in QEMU code, and the case "Operand is smaller
than INT_MIN" is different between SoftFloat and Mips-B, while the case
"Operand is a NaN" is different between SoftFloat and Mips-A.
Aleksandar
From: Maciej Rozycki
Sent: Tues
On Mon, 16 May 2016, Aleksandar Markovic wrote:
> Here one can distinguish three cases:
>
> CASE MIPS-A: (FCR31.NAN2008 == 1)
>
>1. Operand is a NaN, result should be 0;
>2. Operand is larger than INT_MAX, result should be INT_MAX;
>2. Operand is smaller than INT_MIN, result should b
On Mon, May 16, 2016 at 04:12:44PM +0200, Aleksandar Markovic wrote:
> From: Aleksandar Markovic
>
> New set of helpers for handling nan2008-syle versions of instructions
> .., for Mips R6.
>
> All involved instructions have float operand and integer result. Their
> core functionality is impleme
From: Aleksandar Markovic
New set of helpers for handling nan2008-syle versions of instructions
.., for Mips R6.
All involved instructions have float operand and integer result. Their
core functionality is implemented via invocations of appropriate SoftFloat
functions. The problematic cases are
11 matches
Mail list logo
