The entire test suite is passed, but when CI/hw-host runs target/wasefire/applet.wasm, it points out a bug. Unfortunately this WASM module is too big to debug. Maybe you could find the bug in review. I'll try to debug in the meanwhile.

Forgot to ask: How can I enable debug feature when running hwci.sh? I'd like to print logs for the applet.wasm error.

Another approach I tried: I converted it to applet.wast and moved it to the test suite directory, and tried to run spec.rs with it. But its module format/layout seems incompatible, which would require changes in spec.rs.

Forgot to ask: How can I enable debug feature when running hwci.sh?

You can apply the following patch:

diff --git a/scripts/hwci.sh b/scripts/hwci.sh
index 4c222fd0..1f4ac986 100755
--- a/scripts/hwci.sh
+++ b/scripts/hwci.sh
@@ -77,7 +77,7 @@ full() {
 }
 
 case $1 in
-  host) full unix host --arg=--protocol=unix ;;
+  host) full unix host --arg=--protocol=unix --features=wasefire-interpreter/debug ;;
   # P1.01, P1.02, and P1.03 must be connected together (gpio_test).
   nordic) full usb nordic ;;
   *) run --protocol=${1:-usb} "$2" ;;

And then simply run ./scripts/hwci.sh host as usual.

@ia0 I was wondering how to get around the following "cannot borrow *self as mutable more than once at a time" error. Thanks.

In Thread::step(), I basically use the following function to take the jump

fn take_jump(&mut self, ls_idx: Option<usize>, side_tables: &[Vec<SideTableEntry>]) {
    let frame = self.frame();
    let parser = &mut self.parser;
    frame.take_jump(parser, ls_idx, side_tables);
}

where self.frame() returns &mut Frame<'m>.

Yes, that's a common problem in Rust. You'll need to inline the definition of fn frame() instead of calling it.

I'd like to refactor incrementally. After storing side_table: &'m [SideTableEntry] in Frame and making Module::func() return side table additionally, there appear to be three confusing Rust errors when creating Frame. I'm not sure why they occur. Could you take a look at the last commit? Thanks.