nasm/test/uscore.asm

;Testname=test; Arguments=-fbin -ouscore.bin; Files=stdout stderr uscore.bin
	dd 0x1234_5678
	dd 305_419_896		; Same number as above it
	dd 0x1e16		; NOT a floating-point number!
	dd 1e16h		; NOT a floating-point number!
	dd 1e16_h		; NOT a floating-point number!
	dd $1e16		; NOT a floating-point number!
	dd $1e+16		; NOT a floating-point number!
	dd 1e16			; THIS is a floating-point number!
	dd 1e+16
	dd 1.e+16
	dd 1e+1_6
	dd 1e1_6
	dd 1.0e16
	dd 1_0e16		; This is 1e17, not 1e16!
test: change .stdout/.stderr to stdout/stderr Using hidden files are rather antisocial, and rather pointless in this particular context. Change .stdout and .stderr to simply stdout and stderr. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 2008-10-07 09:27:30 +08:00			`;Testname=test; Arguments=-fbin -ouscore.bin; Files=stdout stderr uscore.bin`
Test of underscored constants 2007-10-20 04:14:06 +08:00			`dd 0x1234_5678`
			`dd 305_419_896 ; Same number as above it`
			`dd 0x1e16 ; NOT a floating-point number!`
Don't confuse suffixed hexadecimal with floating-point 1e30 is a floating-point constant, but 1e30h is not. The scanner won't know that until it sees the "h", so make sure we keep enough state to be able to distinguish "1e30" (a possible hex constant) from "1.e30", "1e+30" or "1.0" (unabiguously floating-point.) 2007-10-20 05:10:35 +08:00			`dd 1e16h ; NOT a floating-point number!`
			`dd 1e16_h ; NOT a floating-point number!`
			`dd $1e16 ; NOT a floating-point number!`
uscore.asm: Fix test case "$1e+16" was missing, instead "$1e16" was duplicated 2007-10-20 05:19:52 +08:00			`dd $1e+16 ; NOT a floating-point number!`
Test of underscored constants 2007-10-20 04:14:06 +08:00			`dd 1e16 ; THIS is a floating-point number!`
			`dd 1e+16`
			`dd 1.e+16`
			`dd 1e+1_6`
			`dd 1e1_6`
			`dd 1.0e16`
			`dd 1_0e16 ; This is 1e17, not 1e16!`