mirror of
https://github.com/fadden/6502bench.git
synced 2024-12-02 13:51:36 +00:00
4322a0c231
We currently have two options for assembly code output, selected by a checkbox in the application settings: always put labels on the same lines as the instruction or data operand, or split the labels onto their own line if they were wider than the label text field. This change adds a third option, which puts labels on their own line whenever possible. Assemblers don't generally allow this for variable assignment pseudo-ops like "foo = $1000", but it's accepted for most other situations. This is a cosmetic change to the output, and will not affect the generated code. The old true/false app setting will be disregarded. "Split if too long" will be used by default. Added test 20280-label-placement to exercise the "split whenever allowed" behavior. The "export" function has a similar option that has not been updated (for no particular reason other than laziness). Also, simplified the app settings GetEnum / SetEnum calls, which can infer the enumerated type from the arguments. This should not impact behavior.
30 lines
594 B
ArmAsm
30 lines
594 B
ArmAsm
!cpu 6502
|
|
shortnm = $4000 ;short label
|
|
SomewhatLongName = $4001 ;somewhat longer label
|
|
|
|
* = $1000
|
|
lda shortnm
|
|
ldx SomewhatLongName
|
|
clc
|
|
bcc BranchTargetLongName
|
|
|
|
data
|
|
!byte $cc
|
|
|
|
!zone Z00000a
|
|
.ptr = $00 ;local var with short name
|
|
.PointerWithLongName = $02 ;local var with longer name
|
|
BranchTargetLongName
|
|
sta .ptr
|
|
stx .PointerWithLongName
|
|
ldy data
|
|
lsr
|
|
bcc shortb
|
|
shortb
|
|
nop
|
|
jmp done
|
|
|
|
done
|
|
rts
|
|
|