1
0
mirror of https://github.com/fadden/6502bench.git synced 2024-12-01 22:50:35 +00:00
6502bench/SourceGen/SGTestData/Expected/2011-hinting_64tass.S
Andy McFadden 32d1147eec Improve multi-encoding output in 64tass
Previously, we used the default character encoding from the project
properties to determine how strings and character constants in the
entire source file should be encoded.  Now we switch between
encodings as needed.  The default character encoding is no longer
relevant.

High ASCII is now an actual encoding, rather than acting like ASCII
that sometimes doesn't work.  Because we can do high ASCII character
operands with "| $80", we don't output a .enc to switch from ASCII
to high ASCII unless we need to generate a string.  (If we're
already in high ASCII mode, the "| $80" isn't required but won't
hurt anything.)

We now do a scan up front to see if ASCII or high ASCII is needed,
and only output the .cdefs for the encodings that are actually used.

The only gap in the matrix is high ASCII DCI strings -- the ".shift"
pseudo-op rejects text if the string doesn't start with the high
bit clear.
2019-08-21 13:46:05 -07:00

36 lines
631 B
ArmAsm

.cpu "6502"
* = $1000
.byte $03
.byte $02
L1002 bit L1002
.byte $2c
lda #$11
nop
.byte $2c
L100A ldx #$ff
nop
jsr L100A
nop
.byte $2c
L1012 ldx #$ff
nop
jsr L1012
jsr $2456
L101B .dword $22a211a9
jsr L101B
jsr L1028
jsr $2456
L1028 .dword $44a233a9
jsr L1037
jsr L103A
nop
lda $2456
rts
L1037 jsr $2456
L103A lda #$55
ldx #$66
rts