H. Peter Anvin wrote:
> Okay, it seems pretty clear that NASM 2.04 was a dud. Accordingly, I
> have tagged NASM 2.05rc1 to try to get a bug fix release out quickly.
> Please, people, try to:
>
> a) help test this so we don't end up in the same situation again, and
> b) limit your checkins to bug fixes, or do them on a branch.
Okay, got it pushed out to SF, and "advertised" a little...
My own (fairly limited) testing indicates that the "main problem" (short
jump out of range) is fixed. I'm still seeing warnings on "signed byte
value exceeds bounds" when Nasm is deciding on its own initiative to
optimize, for example "cmp eax, 0FFFFFFFFh", etc... This seems to crop
up quite often (which means it's *doing* something for us!).
Best,
Frank
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
Nasm-devel mailing list
Nasm-devel@...
https://lists.sourceforge.net/lists/listinfo/nasm-devel
