6502bench/SourceGen/SGTestData/Expected/2004-numeric-types_Merlin32.S

;Project file was edited to get all big-endian data types, and to have an
;incorrect .junk alignment directive.
         org   $1000
         rts

         dfb   $11
         dw    $1122
         adr   $112233
         adrl  $11223344
         dfb   $11
         ddb   $1122
         dfb   $11,$22,$33
         dfb   $11,$22,$33,$44
         ds    2,$00
         dfb   $80
         ds    3,$00
         dfb   $80
         ds    4,$00
         dfb   $80
         ds    5,$00
         dfb   $80
         ds    256,$00
         dfb   $80
         ds    257,$cc
         hex   11
         dfb   $80
         hex   11223344556677889900
         dfb   $80
LABEL    hex   00112233445566778899aabbccddeeff00112233445566778899aabbccddeeff ;comment
         hex   00112233445566778899aabbccddeeffffeeddccbbaa99887766554433221100
         dfb   $80
         ds    \,$aa
         dfb   $81
         ds    63,$00
         dfb   $81
         ds    31,$ab
         hex   0000000000000001
         dfb   $81
         hex   1000000000000000
         dfb   $81
         ds    2,$dd      ;incorrect alignment
         ds    \,$00
Add junk/align directives Sometimes there's a bunch of junk in the binary that isn't used for anything. Often it's there to make things line up at the start of a page boundary. This adds a ".junk" directive that tells the disassembler that it can safely disregard the contents of a region. If the region ends on a power-of-two boundary, an alignment value can be specified. The assembly source generators will output an alignment directive when possible, a .fill directive when appropriate, and a .dense directive when all else fails. Because we're required to regenerate the original data file, it's not always possible to avoid generating a hex dump. 2019-10-19 03:28:02 +00:00			`;Project file was edited to get all big-endian data types, and to have an`
			`;incorrect .junk alignment directive.`
Initial file commit 2018-09-28 17:05:11 +00:00			`org $1000`
			`rts`

			`dfb $11`
			`dw $1122`
			`adr $112233`
			`adrl $11223344`
			`dfb $11`
			`ddb $1122`
			`dfb $11,$22,$33`
			`dfb $11,$22,$33,$44`
			`ds 2,$00`
			`dfb $80`
			`ds 3,$00`
			`dfb $80`
			`ds 4,$00`
			`dfb $80`
			`ds 5,$00`
			`dfb $80`
			`ds 256,$00`
			`dfb $80`
			`ds 257,$cc`
			`hex 11`
			`dfb $80`
			`hex 11223344556677889900`
			`dfb $80`
			`LABEL hex 00112233445566778899aabbccddeeff00112233445566778899aabbccddeeff ;comment`
			`hex 00112233445566778899aabbccddeeffffeeddccbbaa99887766554433221100`
			`dfb $80`
Add junk/align directives Sometimes there's a bunch of junk in the binary that isn't used for anything. Often it's there to make things line up at the start of a page boundary. This adds a ".junk" directive that tells the disassembler that it can safely disregard the contents of a region. If the region ends on a power-of-two boundary, an alignment value can be specified. The assembly source generators will output an alignment directive when possible, a .fill directive when appropriate, and a .dense directive when all else fails. Because we're required to regenerate the original data file, it's not always possible to avoid generating a hex dump. 2019-10-19 03:28:02 +00:00			`ds \,$aa`
			`dfb $81`
			`ds 63,$00`
			`dfb $81`
			`ds 31,$ab`
			`hex 0000000000000001`
			`dfb $81`
			`hex 1000000000000000`
			`dfb $81`
			`ds 2,$dd ;incorrect alignment`
			`ds \,$00`