6502/6502bench
1
0
Fork 0
mirror of https://github.com/fadden/6502bench.git synced 2024-07-06 16:29:03 +00:00
Code Issues Projects Releases Wiki Activity
cb114be0f6
6502bench/SourceGen/SGTestData/Expected/20000-numeric-types_cc65.S

99 lines
2.5 KiB
ArmAsm
Raw Normal View History

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
.setcpu "6502"
.org $1000
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
bit L1448
jsr L14A8
nop
nop
nop
nop
nop
nop
nop
nop
nop
nop
nop
nop
nop
nop
nop
nop
Initial file commit
2018-09-28 17:05:11 +00:00
rts
.byte $11
.word $1122
.faraddr $112233
.dword $11223344
.byte $11
.dbyt $1122
.byte $11,$22,$33
.byte $11,$22,$33,$44
.res 2,$00
.byte $80
.res 3,$00
.byte $80
.res 4,$00
.byte $80
.res 5,$00
.byte $80
.res 256,$00
.byte $80
.res 257,$cc
.byte $11
.byte $80
.byte $11,$22,$33,$44,$55,$66,$77,$88,$99,$00
.byte $80
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
LABEL: .byte $00,$11,$22,$33,$44,$55,$66,$77,$88,$99,$aa,$bb,$cc,$dd,$ee,$ff ;comment on bulk
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00,$11,$22,$33,$44,$55,$66,$77,$88,$99,$aa,$bb,$cc,$dd,$ee,$ff
.byte $00,$11,$22,$33,$44,$55,$66,$77,$88,$99,$aa,$bb,$cc,$dd,$ee,$ff
.byte $ff,$ee,$dd,$cc,$bb,$aa,$99,$88,$77,$66,$55,$44,$33,$22,$11,$00
.byte $80
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
.res 115,$aa
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
.byte $81
.res 63,$00
.byte $81
.res 31,$ab
.byte $00,$00,$00,$00,$00,$00,$00,$01
.byte $81
.byte $10,$00,$00,$00,$00,$00,$00,$00
.byte $81
.res 2,$dd ;incorrect alignment
.res 140,$00
Correct handling of no-op .ORG statements These were being overlooked because they didn't actually cause anything to happen (a no-op .ORG sets the address to what it would already have been). The assembly source generator works in a way that causes them to be skipped, so everybody was happy. This seemed like the sort of thing that was likely to cause problems down the road, however, so we now split regions correctly when a no-op .ORG is encountered. This affects the uncategorized data analyzer and selection grouping. This changed the behavior of the 2004-numeric-types test, which was visibly weird in the UI but generated correct output. Added the 2024-ui-edge-cases test to provide a place to exercise edge cases when testing the UI by hand. It has some value for the automated regression test, so it's included there. Also, changed the AddressMapEntry objects to be immutable. This is handy when passing lists of them around.
2020-02-28 22:43:03 +00:00
.res 8,$82
.org $1408
.res 8,$82 ;note no-op .ORG
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
.res 8,$83
.org $1428
Correct handling of no-op .ORG statements These were being overlooked because they didn't actually cause anything to happen (a no-op .ORG sets the address to what it would already have been). The assembly source generator works in a way that causes them to be skipped, so everybody was happy. This seemed like the sort of thing that was likely to cause problems down the road, however, so we now split regions correctly when a no-op .ORG is encountered. This affects the uncategorized data analyzer and selection grouping. This changed the behavior of the 2004-numeric-types test, which was visibly weird in the UI but generated correct output. Added the 2024-ui-edge-cases test to provide a place to exercise edge cases when testing the UI by hand. It has some value for the automated regression test, so it's included there. Also, changed the AddressMapEntry objects to be immutable. This is handy when passing lists of them around.
2020-02-28 22:43:03 +00:00
.res 8,$83 ;meaningful .ORG
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
.res 8,$84
UserLabel: .res 8,$84
.res 8,$85
L1448: .res 8,$85
.res 16,$86
.res 8,$87
;long comment
.res 8,$87
.res 16,$88
.res 8,$89
.res 8,$89
.res 8,$8a
.res 8,$8a
.res 8,$8b
L14A8: .res 8,$8b
.res 8,$8c
.byte %10001100
.res 7,$8c
Add "uninitialized data" format type This allows regions that hold variable storage to be marked as data that is initialized by the program before it is used. Previously the choices were to treat it as bulk data (initialized) or junk (totally unused), neither of which are correct. This is functionally equivalent to "junk" as far as source code generation is concerned (though it doesn't have to be). For the code/data/junk counter, uninitialized data is counted as junk, because it technically does not need to be part of the binary.
2021-10-13 21:48:05 +00:00
.byte $90
.byte $92,$91
.byte $95,$94,$93
.byte $99,$98,$97,$96
.res 1,$00
.res 2,$00
.res 3,$00
.res 4,$00
.byte $80
.res 5,$00
.byte $80
Reference in New Issue Copy Permalink