CKB-VM asm64 and interpreter64 modes report inconsistent errors

[Subway2023]

Describe the bug
When running the same RISC-V program on CKB-VM, the error results differ between asm64 mode and interpreter64 mode.

To Reproduce

.text
.globl _start
_start:
    li x15, -300
    li x16, 600
    xori x17, x15, -750
    andi x18, x16, 31
    sra x19, x17, 4
    bgeu x19, x18, path1
    beq x15, x16, path2
    or x20, x17, x18
    j exit
path1:
    li x21, 7
    j exit
path2:
    li x22, 8
exit:
    li x23, 0
    jalr x0, x23, 0

1. compiler

riscv64-unknown-elf-gcc -nostdlib -march=rv64imc -mabi=lp64 -o test.elf  test.s

2. run with asm mode

ckb-vm/target/debug/examples/ckb_vm_runner --mode asm64 test.elf

exit=Err(MemWriteOnExecutablePage(0))
cycles=16
r[a1]=0
registers=[0, 0, 4194288, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 18446744073709551316, 600, 966, 24, 60, 0, 7, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]

3. run with interpreter mode

ckb-vm/target/debug/examples/ckb_vm_runner --mode interpreter64 test.elf

exit=Err(InvalidInstruction { pc: 0, instruction: 0 })
cycles=16
r[a1]=0
registers=[0, 0, 4194288, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 18446744073709551316, 600, 966, 24, 60, 0, 7, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]

[mohanson]

ckb-vm does not guarantee that asm and interpreter modes always output consistent errors, due to the significant differences between these two execution modes. Specifically, ckb-vm's consistency guarantees hold in the following scenarios:

• When asm returns an exit code normally, interpreter mode should also return a consistent exit code.
• When interpreter returns an exit code normally, asm mode should also return a consistent exit code.
• When asm returns an error, interpreter should also return an error, but the error is not guaranteed to be consistent with asm's.
• When interpreter returns an error, asm should also return an error, but the error is not guaranteed to be consistent with interpreter's.