Open OlivierBBB opened 2 months ago
we introduced LEQ
and GEQ
for WCP
too. He's not dealing with only EVM's instructions.
@letypequividelespoubelles yes
So, currently there is a display
option :opcode
. You're thinking of something like that?
The following modules MMU / MMIO / OOB / EXP / ... have their own "instruction sets" independent of the EVM's instruction set, see the respective specifications. These are typically 2 byte integers (to differentiate them from the 1 byte opcodes of the EVM.) It would be great help if we could annotate these columns in
corset
to display the associated instruction names incorset inspect
. The current state of things makes it hard to deciper what is going on.Here is an example from the MMU module. The MMU module has 3 "instruction" columns
macro/MMU_INST
column it gets from the HUB, it contains values from the MMU's instruction setmicro/MMIO_INST
column it provides the MMIO module with, containing values from the MMIO's instruction setwcp/INST
column it provides the WCP module with, containing regular EVM instructionsThe stuff below is supposed to represent the sequence of MMU instructions the HUB creates in response to dealing with
KECCAK
,MSTORE
,KECCAK
,MSTORE
,LOG2
,REVERT
(withLOG2
deliberately not drawn due to reverting andREVERT
missing ~for reasons I'm still investigating~ due to this being the root context of the transaction.)