Pseudo-instructions are not explicitly differentiated from real instructions in the generated instruction dictionary. Moreover they lack information about their origin (parent) instructions.
Although this might not be needed by most downstream repos, which I assume don't use pseudo instruction, the lack of differentiation makes it really hard when this information is needed. I think this could be solved by either creating a separate dictionary just for pseudo or of just by adding a 'is_pseudo' and a 'origin_instruction' to the dictionary. I'm more inclined to the second approach since it will only minimally affect the repo code base and ouputs.
Pseudo-instructions are not explicitly differentiated from real instructions in the generated instruction dictionary. Moreover they lack information about their origin (parent) instructions.
Although this might not be needed by most downstream repos, which I assume don't use pseudo instruction, the lack of differentiation makes it really hard when this information is needed. I think this could be solved by either creating a separate dictionary just for pseudo or of just by adding a 'is_pseudo' and a 'origin_instruction' to the dictionary. I'm more inclined to the second approach since it will only minimally affect the repo code base and ouputs.