Chris Fallin

@misapprehand the `run-experimental-x64-ci.sh` script uses nightly Rust (see in the script the `$CARGO_VERSION` variable), so you'll need to install the `wasm32-wasi` target for nightly as well: `rustup target add --toolchain...

So I think there are two separable issues here: (i) use of the frame pointer, and (ii) loads of stack arguments. On (i) the frame pointer, we have ongoing discussions...

Yes, I agree that making everything relative to FP would be substantially simpler here: it would let us translate spillslot addresses without regard to emission state (nominal-SP offset) in the...

@tiran thanks for the report! We currently don't have anyone on the project who understands our DWARF-handling code well and has time to work on it; so while this is...

Hi @yuyang-ok -- thanks for this! I will take a detailed look next week when I'm back in the office. At a high level, my initial feedback is that new...

hi @yuyang-ok -- no, not yet; I just got back this morning. I would expect this to take some time, especially for a 21k-line PR. At a high level, though,...

@yuyang-ok unfortunately, I still have not gotten to it, sorry. It looks like you still have code in legacy handwritten lowerings, though you're slowly moving it over to ISLE --...

@yuyang-ok a port of `wasmtime`'s CPU-dependent bits -- the fiber library, and the trap handler details, at least -- would probably not be too much work beyond a pure Cranelift-only...

> @cfallin @bjorn3 @afonso360 @afonso360 I think it's the time to review.I think I fix most of the problems. @yuyang-ok I scanned through the diff at places where I had...

> wasmtime is not fully workd,because rusty_v8 cannot be compiler on riscv64. That's fine, as @bjorn3 mentions above V8 is only needed for one fuzzing target. You can disable it...