Open clarus opened 2 months ago
With a check into the function signature of execute_instruction
, I think the task can be divded based on the types appeared in the signature. I'm creating issues based on them:
fn execute_instruction(
pc: &mut u16,
locals: &mut Locals,
ty_args: &[Type],
function: &Arc<Function>,
resolver: &Resolver,
interpreter: &mut Interpreter,
gas_meter: &mut impl GasMeter,
instruction: &Bytecode,
) -> PartialVMResult<InstrRet> { ... }
OK, good idea!
Write a simulation for the evaluation function
execute_instruction
in https://github.com/move-language/move-sui/blob/main/crates/move-vm-runtime/src/interpreter.rsThere might be a lot of dependencies to this function, that can be cut into smaller pull requests!