To make sure that those who follow this list, but not the
bug tracking
list, are included, I would like opinions on the following
issue raised
by bug 1915134.
As a consequence of upgrading the expression evaluator to
64-bits, the
range of values from 0FFFFFFFFh to 080000000h (and their
equivalent
representations in other bases), which used to be evaluated
as negative
numbers, are now evaluated as positive numbers. There seem
to be three
viable choices:
1. Change only the documentation.
2. Special case the optimization code to test the current
BITS mode.
3. Change the evaluator to sign-extend these values based on
the current
BITS setting.
I am also raising this issue in clax86, to give our users a
chance to
provide their input.
--
Chuck
htt
p://www.pacificsites.com/~ccrayne/charles.html
------------------------------------------------------------
-------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
a>
_______________________________________________
Nasm-devel mailing list
Nasm-devel lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nasm-devel
a>
|