Alessandro Gatti

Regarding the fact that RV64 cores usually come with an FPU on board and whatnot... Would a PR that bakes in the extensions set an MPY file is built for...

> I understand the motivation here (eg `armv7emsp` and `armv7emdp` would be just `armv7m` plus floating-point features), but (1) how exactly do you propose to do that, how would the...

Sure, I've rebased it and CI didn't detect any failures for the QEMU/RV64 job. It should be ready for review.

Sorry, last minute change in the semihosting asm block (wrong offset for the exit code, now fixed).

I'm not sure Arch's toolchain is able to generate a working image. Arch's toolchain support libraries haven't been compiled for the `medany` memory model, which allows for code being placed...

The only workaround I found to make it work with that toolchain is to figure out how to make the MicroPython image work when used as the machine's BIOS -...

I've tried quite a few toolchains and short of rebuilding the one from https://github.com/riscv-collab/riscv-gnu-toolchain using `./configure --with-arch=rv64imac --with-cmodel=medany`, the one from Ubuntu that's also used in the CI is probably...

For the record, here's how much space the container image takes on my machine: ```bash $ podman image tree mpy-qemu-riscv Image ID: 12989dfa2914 Tags: [localhost/micropython/mpy-qemu-riscv:latest] Size: 6.89GB Image Layers ├──...

> I ran the `podman container create` command from the README, and that seemed to work (it returned a big hash). That's correct, the hash is the id of the...

In the case of the filesystem permissions issues you've seen, if I don't add that argument things don't work on my end and I wonder if it is due to...