Mohanson

The assembly code for the JIT uses the `System V AMD64 ABI`, which means that this assembly cannot run on windows64. https://en.wikipedia.org/wiki/X86_calling_conventions I will make the code windows compatible

There are some bugs in numext-fixed-uint = 0.1.2, I will update it on muta. ref: https://github.com/cryptape/rust-numext/issues/36 ref: https://github.com/cryptape/rust-numext/issues/34

I can't reproduce your problem, this code works fine on my computer. Perhaps you should provide more informations.

You are right. I reproduced this issue with nodejs, but I'm not yet able to identify the cause of the problem. ```js const fs = require('fs') const wasmBuffer = fs.readFileSync('/tmp/pikchrNoImp.wasm')...

A few days ago, I almost completely rewrote pywasm and released pywasm 2.0 https://github.com/mohanson/pywasm/releases/tag/v2.0.0 I re-ran the problem code provided by this issue, and now the results provided by pywasm...

Pywasm 1.0 was originally written in webassembly 0.8. It may be inconsistent with the current webassembly in some places, and it is difficult for me to find the difference, so...

Weird tutorial, I don't remember ever writing code like this for pywasm. If you want to pass in an array to wasm via python, remember one thing, any data is...

The input refers to random RISC-V binary code. It may be legal RISC-V binary code, but it may also be illegal. We use `run_asm` and `run_int` to test this randomly...

I think executing the following command can solve your problem: ```sh $ sudo apt install device-tree-compiler ``` If you still encounter problems, you can try to manually execute the `build.sh`...

> The input for fuzzing is RISC-V binary code. Do you happen to have a differential testing tool that accepts RISC-V assembly code as input instead? This would make it...