mirror of
https://github.com/fadden/6502bench.git
synced 2024-08-14 18:28:57 +00:00
This worked, sort of. The problem is that SourceGen will revert to hex output in certain situations, such as a broken symbolic reference. There happens to be one in the ZIPPY example, and it's on a relative branch. The goal with the segment stuff is to allow cc65 to treat the source as relocatable code. In that context, a relative branch to an absolute address doesn't make any sense, so the assembler reports a range error. We don't currently have a mechanism that guarantees no references are broken (and no affordance for finding them), so we can't make this mode the default yet. Instead, we continue to use the generic config, but generate the correct set of lines as comments. (issue #39)
35 lines
1.0 KiB
ArmAsm
35 lines
1.0 KiB
ArmAsm
;Project file was edited to get all big-endian data types.
|
|
.setcpu "6502"
|
|
; .segment "SEG000"
|
|
.org $1000
|
|
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
|
|
LABEL: .byte $00,$11,$22,$33,$44,$55,$66,$77,$88,$99,$aa,$bb,$cc,$dd,$ee,$ff ;comment
|
|
.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
|