6502/6502bench
1
0
Fork 0
mirror of https://github.com/fadden/6502bench.git synced 2024-12-12 05:31:04 +00:00
Code Issues Projects Releases Wiki Activity
07f5396eee
6502bench/SourceGen/SGTestData/Expected/20270-std-inline_cc65.S

103 lines
1.9 KiB
ArmAsm
Raw Normal View History

Add "StdInline" extension script Inline strings and 16-bit addresses are sufficiently common that a general-purpose extension script is useful.
2021-10-16 18:36:13 +00:00
.setcpu "6502"
Ignore project/platform symbols in StdInline External symbols don't have a file offset, so a JSR to an external address can't reliably be matched to a label.
2021-10-28 03:23:34 +00:00
InW_project = $e000
Add "StdInline" extension script Inline strings and 16-bit addresses are sufficiently common that a general-purpose extension script is useful.
2021-10-16 18:36:13 +00:00
.org $1000
jmp L1040
InAZ_test: rts
InA1_test: rts
InPZ_test: rts
InP1_test: rts
InW_test: rts
InWA_test: rts
InNR_test: rts
.res 54,$00
L1040: nop
jsr InAZ_test
.asciiz "Test AZ_ low"
jsr InAZ_test
.byte $d4,$e5,$f3,$f4,$a0,$c1,$da,$df,$a0,$e8,$e9,$e7,$e8,$00
jsr InA1_test
.byte $0c,"Test A1_ low"
jsr InA1_test
.byte $0d,$d4,$e5,$f3,$f4,$a0,$c1,$b1,$df,$a0,$e8,$e9,$e7,$e8
jsr InPZ_test
.byte $d4,$45,$53,$54,$20,$d0,$da,$5f,$00
jsr InP1_test
.byte $08,$d4,$45,$53,$54,$20,$d0,$31,$5f
jsr InW_test
.word $1234
jsr InWA_test
.word L1040
jsr @L10AD
jsr InNR_test
.byte $ea
.byte $00
@L10AD: nop
Correct StdInline behavior for overlapping addresses The implementation was mapping labels to addresses, then formatting inline data at the matching address. This may be incorrect when there are multiple sections of the file mapped to the same address. The correct approach is to record the offsets of the matching labels, and then do an address-to-offset translation for each JSR. Also, show a note in the Info window when a JSR has been marked no-continue by an extension script. Also, updated Daily Tips.
2021-10-27 21:18:52 +00:00
jsr InW_test1
.word $1100
nop
Ignore project/platform symbols in StdInline External symbols don't have a file offset, so a JSR to an external address can't reliably be matched to a label.
2021-10-28 03:23:34 +00:00
jmp L4000
Correct StdInline behavior for overlapping addresses The implementation was mapping labels to addresses, then formatting inline data at the matching address. This may be incorrect when there are multiple sections of the file mapped to the same address. The correct approach is to record the offsets of the matching labels, and then do an address-to-offset translation for each JSR. Also, show a note in the Info window when a JSR has been marked no-continue by an extension script. Also, updated Daily Tips.
2021-10-27 21:18:52 +00:00
.byte $80
.org $2000
InW_test1: nop
jsr InW_test1
.word $1200
rts
.byte $80
.org $2000
InW_test2: nop
jsr InW_test2
.word $1300
rts
.byte $80
.org $2000
not_inline: nop
jsr not_inline
bit not_inline
rts
.byte $81
.org $0000
InW_na_test: .byte $ea
.byte $20
.byte $00
.byte $30
.byte $60
.byte $81
Ignore project/platform symbols in StdInline External symbols don't have a file offset, so a JSR to an external address can't reliably be matched to a label.
2021-10-28 03:23:34 +00:00
.org $4000
L4000: bit L4000
jsr InW_project
jmp @LF000
Correct StdInline behavior for overlapping addresses The implementation was mapping labels to addresses, then formatting inline data at the matching address. This may be incorrect when there are multiple sections of the file mapped to the same address. The correct approach is to record the offsets of the matching labels, and then do an address-to-offset translation for each JSR. Also, show a note in the Info window when a JSR has been marked no-continue by an extension script. Also, updated Daily Tips.
2021-10-27 21:18:52 +00:00
.org $f000
Ignore project/platform symbols in StdInline External symbols don't have a file offset, so a JSR to an external address can't reliably be matched to a label.
2021-10-28 03:23:34 +00:00
@LF000: jsr @LF008
Correct StdInline behavior for overlapping addresses The implementation was mapping labels to addresses, then formatting inline data at the matching address. This may be incorrect when there are multiple sections of the file mapped to the same address. The correct approach is to record the offsets of the matching labels, and then do an address-to-offset translation for each JSR. Also, show a note in the Info window when a JSR has been marked no-continue by an extension script. Also, updated Daily Tips.
2021-10-27 21:18:52 +00:00
jsr @LF015
Add "StdInline" extension script Inline strings and 16-bit addresses are sufficiently common that a general-purpose extension script is useful.
2021-10-16 18:36:13 +00:00
nop
rts
Correct StdInline behavior for overlapping addresses The implementation was mapping labels to addresses, then formatting inline data at the matching address. This may be incorrect when there are multiple sections of the file mapped to the same address. The correct approach is to record the offsets of the matching labels, and then do an address-to-offset translation for each JSR. Also, show a note in the Info window when a JSR has been marked no-continue by an extension script. Also, updated Daily Tips.
2021-10-27 21:18:52 +00:00
@LF008: jsr InA1_test
Add "StdInline" extension script Inline strings and 16-bit addresses are sufficiently common that a general-purpose extension script is useful.
2021-10-16 18:36:13 +00:00
.byte $ff
.byte "too long"
.byte $ea
Correct StdInline behavior for overlapping addresses The implementation was mapping labels to addresses, then formatting inline data at the matching address. This may be incorrect when there are multiple sections of the file mapped to the same address. The correct approach is to record the offsets of the matching labels, and then do an address-to-offset translation for each JSR. Also, show a note in the Info window when a JSR has been marked no-continue by an extension script. Also, updated Daily Tips.
2021-10-27 21:18:52 +00:00
@LF015: jsr InAZ_test
Add "StdInline" extension script Inline strings and 16-bit addresses are sufficiently common that a general-purpose extension script is useful.
2021-10-16 18:36:13 +00:00
.byte "does not end"
Reference in New Issue Copy Permalink