Closed phillipeaton closed 1 year ago
Additional feedback: If I leave the multilabel option on
, some of my labels don't make it into the generated source code file and the later assembly fails. (I recall seeing some warnings somewhere about multilabel, there may be gotchas.)
After seeing the below comment with the context of the other thread, I think that multilabel doesn't work in the way I am expecting, as described earlier in this thread.
You can therefore either Close this Issue or consider it as a Feature Request that I would find very useful!
You can either write
label 0d ZP_Color_RAM_PtrX+1
or tell dasmfw that multiple labels are allowed for an address by setting
option multilabel on
I'd suggest the first, however - using multiple labels for an address opens a can of very ugly worms.
Originally posted by @Arakula in https://github.com/Arakula/dasmfw/issues/13#issuecomment-1171112837
Moved to Feature suggestion: Show Label Call Addresses
In the Disassembler Options documentation, it has:
If I set this to
on
with a 6502 disassembly, it doesn't seem to do anything...but I'm not sure exactly what it should be doing.The picture below is from the Infiltrator disassembler, it's created mulitple labels for $8100 (which is on line 211), I'm assuming dasmfw
multilabel
does something similar regarding multiple labels?The picture below is some 6502 code produced by dasmfw with
multilabel on
, there are multiple calls to a single addressTJOC_RTS
, but only a single label produced.My info options file is:
Any clues?