Support for ARM32

[jiayihu]

I'm evaluating if wasmer can be used for embedded systems, but it seems that for now it supports only Aarch64 (such as raspberry pi). Is there any plan to support ARM32? Supporting raspberry pi is of limited interest, most of boards have much less memory. For instance I'm using a STM32F429 with 2MB flash and 192KB RAM

[nicodemus26]

I'd also like to run on arm32/armhf/armv7l, particularly the i.MX6 series from Freescale/NXP. These are pretty widely-deployed processors for embedded applications, and I think you'd get a lot of traction in embedded use of wasmer with 32-bit arm support.

[emrahayanoglu]

This is very crucial feature to provide FaaS via webassembly to the IoT devices as most of the devices in the field is based on arm32/armhf/armv7.
Any plans or any documentation that we can involve on development for the related feature to be provided to the wasmer?

[cinerea0]

Chiming in to agree that it would be great to have this available for armv6 and armv7. In addition to IoT applications, there are Linux distributions that target those platforms along with x86 that prefer that their packages build on all of their supported platforms.

[Hywan]

Edit: Sorry for the super late reply. I don't know how I missed this issue before…

If you use our LLVM based compiler (wasmer-compiler-llvm), then it's possible to target arm32, armhf, armv7l etc.

Our Cranelift based compiler (wasmer-compiler-cranelift) only supports arm64 for the moment.

Our Singlepass based compiler (wasmer-compiled-singlepass) only supports arm64 for the moment, but it was supporting arm32 in the past. There is an ongoing work to backport this feature.

[Hywan]

Bonus: see https://github.com/wasmerio/wasmer/blob/master/examples/engine_cross_compilation.rs to cross-compile to any platforms/architectures you want.

See https://github.com/wasmerio/wasmer/blob/master/examples/compiler_llvm.rs to learn how to use the LLVM compiler if needed.

[Hywan]

Note: But wasmer-vm doesn't support arm32 and so on for the moment.

[syrusakbary]

Closing this in favor of #2324