nasm/test/br3058845.asm

;Testname=unoptimized; Arguments=-O0 -fbin -obr3058845.bin; Files=stdout stderr br3058845.bin
;Testname=optimized;   Arguments=-Ox -fbin -obr3058845.bin; Files=stdout stderr br3058845.bin

BITS 16
cmp ax, 0xFFFF
cmp eax, 0xFFFF_FFFF

BITS 32
cmp ax, 0xFFFF
cmp eax, 0xFFFF_FFFF

BITS 64
cmp ax, 0xFFFF
cmp eax, 0xFFFF_FFFF
BR3058845: mostly fix bogus warning with implicit operand size override The implicit operand size override code didn't set the operand size prefix, which confused the size calculation code for the range check. The BITS 64 operand size calculation is still off, but "fixing" it by making it 32-bit unless REX.W is set breaks PUSH and maybe others. 2010-11-08 02:56:14 +08:00			`;Testname=unoptimized; Arguments=-O0 -fbin -obr3058845.bin; Files=stdout stderr br3058845.bin`
			`;Testname=optimized; Arguments=-Ox -fbin -obr3058845.bin; Files=stdout stderr br3058845.bin`

			`BITS 16`
			`cmp ax, 0xFFFF`
			`cmp eax, 0xFFFF_FFFF`

			`BITS 32`
			`cmp ax, 0xFFFF`
			`cmp eax, 0xFFFF_FFFF`

			`BITS 64`
			`cmp ax, 0xFFFF`
Move implicit operand size override logic to calc_size It is more logical, it cleans up the code and it makes implicit operand size override prefixes come out in the same order as explicit ones instead of after all other prefixes. Suggested-by: H. Peter Anvin <hpa@zytor.com> 2010-12-30 01:13:38 +08:00			`cmp eax, 0xFFFF_FFFF`