vshymanskyy

Geroyam Slava!

Yes, for these microcontroller-type chips, ahead-of-time compilation would be definitely more suitable. WAMR probably supports it, but you can also to it via WASM2C, easily. I prefer not depending on WAMR, it is very bloated

Correct. I didn't create the tagline, sorry

Yes, Wasm3 also targets Cortex-M4 and even Cortex-M0 :)

Wasm3 happily runs on ESP32, it provides a fully dynamic wasm runtime. But it's much slower than AOT compiled native code, obviously.

This is exactly what wasm2mpy does for MicroPython: Dynamically loaded, AOT-compiled WASM modules

Yes, we're talking about Raspberry Pi Pico (RP2040) here. Not the Linux-based SBCs (Single Board Computers)

I don't think .pyc files can contain native code, but .mpy can! And that's exactly what I'm using here:

- compile any language to wasm

- translate wasm to C99

- use the native target toolchain to compile C99 to .mpy

- run that on the device

Thanks for the feedback. I'll improve the README based on your inputs. I was focused on the actual research. Overall, this allows writing code in statically compiled languages and running it (fast) on embedded systems with MicroPython. MicroPython itself is comparatively slow, and this provides tools to deliver more demanding software (AI, signal processing, etc).

With this approach, wasm is compiled to native code. Translating that to Python is in theory possible, but very impractical.

Author here, ready to answer any questions.