Re: Immediate arguments optimizer fails

H. Peter Anvin wrote:
> 
> No, that's bunk.  The whole point of the optimizer is
so the programmer 
> doesn't have to deal with that kind of junk.
> 

The more I think about it, I think the right answer is to
split the 
SBYTE flag into SBYTE2, 4, and 8; that way we can continue
to use the 
front-loaded optimizer.

In the long term, it would be better to have a more
trial-and-error 
optimizer (since we do trial-and-error matching anyway),
that way the 
optimizer should also be able to deal with stuff like:

	bits 64
	mov rax,80000000h

... which should be capable of generate a 7-bit form.

By the way, "mov rax,dword blah" is broken in the
current version...

	-hpa

------------------------------------------------------------
-------------
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/
_______________________________________________
Nasm-devel mailing list
Nasm-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nasm-devel

>         bits 64
>         mov rax,80000000h
>
>  ... which should be capable of generate a 7-bit form.

Ahem... which particular encoding do you have in mind?

(It can't be 48,C7,C0,00,00,00,80 -- because 8000_0000
is not equal to sign-extended 8000_0000.)

------------------------------------------------------------
-------------
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/
_______________________________________________
Nasm-devel mailing list
Nasm-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nasm-devel