6502/6502bench
1
0
Fork 0
mirror of https://github.com/fadden/6502bench.git synced 2024-12-01 22:50:35 +00:00
Code Issues Projects Releases Wiki Activity
37855c8f8e
6502bench/SourceGen/SGTestData/Expected/2013-notes-and-comments_cc65.S

75 lines
3.2 KiB
ArmAsm
Raw Normal View History

Initial file commit
2018-09-28 17:05:11 +00:00
;***************************************
;* Old school boxed output header. *
;* Brk *
;* multiple lines yay. How about a *
;* hy-phenated word? *
;* Looonglonglonglonglonglonglonglongl *
;* onglonglongword. *
;***************************************
;* Throw in a line divider. These *
;* aren't: *
;* *! *
;* * *
;* &XYZ *
;* *
;***************************************
.setcpu "6502"
plataddr = $3000 ;address only in platform file
;Short, unboxed comment here!!
; Two spaces after. More hyp-
;hens?
Attempt to generate segment names for cc65 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)
2018-11-18 22:36:03 +00:00
; .segment "SEG000"
Initial file commit
2018-09-28 17:05:11 +00:00
.org $1000
lda #$01 ;Comment!
;Comment rulers can be helpful in findin the edges of notes. Comments are hyph-
;enatingly fun. Like the note, this goes out to 80 columns.
lda #$02 ;&another comment with &&s!
;Down to 64 columns this time. Why 64? Why not 64. A rose, by
;any other name, would break the line at the same place. Or hy-
;phen split.
lda #$03
;Ah, the classic 40-column limitation...
;brings back memories. Of, you know, h-
;yphenated things.
lda #$04
;Thirty columns. 'cause forty
;felt like too many. Oh, hyp-
;henation!
lda #$05
;*******************************************************************************
;* Short box comment, 80 cols. *
;*******************************************************************************
lda #$06
;***************************************************************
;* *
;* Choppy *
;* *
;* box *
;* *
;* comment *
;* *
;* 64 cols *
;* *
;***************************************************************
lda #$07
;*****************************
;* Some non-ASCII stuff: *
;* †•<E280A0>␇ *
;*****************************
lda #$08
lda #$09
lda #$0a
lda #$0b
lda #$0c
lda #$0d
lda #$0e
lda #$0f
bit plataddr ;Pull in plataddr to see the comment on the platform file entry.
rts
bytes: .byte $00,$01,$02,$03,$04,$05,$06,$07,$08,$09,$0a,$0b,$0c,$0d,$0e,$0f ;Comment at the end of a lengthy bulk hex item might overflow various things, but could be wrapped.
.byte $00,$01,$02,$03,$04,$05,$06,$07,$08,$09,$0a,$0b,$0c,$0d,$0e,$0f
.byte $00,$01,$02,$03,$04,$05,$06,$07,$08,$09,$0a,$0b,$0c,$0d,$0e,$0f
.byte $00,$01,$02,$03,$04,$05,$06,$07,$08,$09,$0a,$0b,$0c,$0d,$0e,$0f
Reference in New Issue Copy Permalink