Use the datamodel returned from Leguan, instead of reparsing the code string again. Currently both parsers use their own models. Here are the reasons why it is not done yet/ what blocks this issue:
Mayor
When use Rm/ Rt (R-Format Instructions define a 4th parameter register: Rm - does this register also goes onto the data path for Rt? All other formats are not affected by that)
Minor
how is FlagRegister sent through pipeline?
how many bytes are accessed by the instruction? (name indicates the size, but how is it sent? own 'cable'?)
how is determined if memory access exclusive? (LDXR)
Use the datamodel returned from Leguan, instead of reparsing the code string again. Currently both parsers use their own models. Here are the reasons why it is not done yet/ what blocks this issue:
Mayor
Minor