diff options
author | Joseph Myers <joseph@codesourcery.com> | 2020-05-15 21:20:25 +0000 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2020-06-10 12:10:26 -0400 |
commit | c8af85b10c818709755f5dc8061c69920611fd4c (patch) | |
tree | 5b61a69a88ed51a6fdedffd0cad0028362eb5e49 /tests/test-rcu-list.c | |
parent | 374ff4d0a3c2cce2bc6e4ba8a77eaba55c165252 (diff) |
target/i386: fix fisttpl, fisttpll handling of out-of-range values
The fist / fistt family of instructions should all store the most
negative integer in the destination format when the rounded /
truncated integer result is out of range or the input is an invalid
encoding, infinity or NaN. The fisttpl and fisttpll implementations
(32-bit and 64-bit results, truncate towards zero) failed to do this,
producing the most positive integer in some cases instead. Fix this
by copying the code used to handle this issue for fistpl and fistpll,
adjusted to use the _round_to_zero functions for the actual
conversion (but without any other changes to that code).
Signed-off-by: Joseph Myers <joseph@codesourcery.com>
Message-Id: <alpine.DEB.2.21.2005152119160.3469@digraph.polyomino.org.uk>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tests/test-rcu-list.c')
0 files changed, 0 insertions, 0 deletions