Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AOT Zephyr support #4051

Open
jucm8 opened this issue Jan 24, 2025 · 1 comment
Open

AOT Zephyr support #4051

jucm8 opened this issue Jan 24, 2025 · 1 comment

Comments

@jucm8
Copy link

jucm8 commented Jan 24, 2025

I'm currently testing AOT in Zephyr, and I'm struggling to understand some things.

This readme states that AOT does not work on the ESP32C3. Can someone explain the reason why this is the case? What is the difference between the qemu_riscv32 and ESP32C3 platforms, so that AOT works on the former, but not on the latter?

Also, is there any kind of compatibility table, which shows what Zephyr platforms support each feature?

Thank you.

@TianlongLiang
Copy link
Collaborator

Generally speaking, even though it's the same architecture, the toolchain for an embedded device will differ from a normal desktop
one(In your case, could be riscv32-esp-elf-gcc vs riscv32-unknown-elf-gcc).
The Memory layout and elf section will all be different, resulting in AOT works on one target, but not on the other.

I am not sure whether esp32c3 is still unsupported right now, you can try it out to see its current status.

Also, is there any kind of compatibility table, which shows what Zephyr platforms support each feature?

The Zephyr platform is a rather vague term that the actual support really depends on the board config, I would say most wasm language features are supported, but some runtime features like Zephry user mode, and threading depend on the actual hardware.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants