Disassembler option? about customasm HOT 4 OPEN

This would be incredibly cool, indeed! But with instructions being as free-form as they are now, I imagine it wouldn't be possible to do a reverse mapping so easily in general... Maybe only for a subset of instructions with simple representations?

About the parameter type specifications, please see here while I haven't got the proper documentation done!

from customasm.

i think the most difficult part would be dealing with Tokens. as they are the only things that effect the actual instruction mnemonic.
and maybe this could be done with an intermediate step that takes the CPU file and gets rid of all tokens before it disassembles a file?

so basically a de-tokenizer.
for example, this could be in the input CPU file:

#tokendef FLAGS
    {
        Z	= 0
        C	= 1
        N	= 2
    }

JR {fl:FLAGS} {src}		-> 0xE[3:0] @ fl[3:0] @ (src - pc)[15:0]

and it would take that and tear it apart into it's seperate possibilites:

JR Z {src}			-> 0xE0[7:0] @ (src - pc)[15:0]
JR C {src}			-> 0xE1[7:0] @ (src - pc)[15:0]
JR N {src}			-> 0xE2[7:0] @ (src - pc)[15:0]

which should make mapping a lot easier. (i assume)
values shouldn't be as difficult since you're taking a number from the binary file and display it... as a number, likely in HEX.

another thing that i would see as difficult would be labels, since the assembler itself has no idea what each instruction does it would be impossible to figure out where to put labels...

unless the CPU file would somehow allow you to specify what instructions are conditional branches, subroutine calls, and returns. since those 3 are the only ones required to implement such an automatic labeling system.

anyways, it seems like a fun "little" challange to reverse this assembler somehow,

from customasm.

Both issues closed ? Nobody working on this ? I 'm considering to implement this as a part of my custom cpu project ...
Somebody interested ? (by the way - brilliant project :_)

from customasm.

No, this issue isn't closed yet. It's just kind of a difficult-to-implement feature, so not really a priority. 😅

from customasm.