On 10/12/21 2:31 AM, Alex Bennée wrote:
For the 4 byte instruction case we started doing an ld_code2 and then reloaded the data with ld_code4 once it was identified as a 4 byte op. This is confusing for the plugin hooks which are expecting to see simple sequential loading so end up reporting a malformed 6 byte instruction buffer.
I think the plugin stuff could be more clever, knowing where the read occurs within the sequence. Otherwise, we should simplify the interface so that it is not possible to make this mistake.
r~
