zoraaver

Is there an update on this? Batch builds would be really useful to avoid starting multiple codebuild jobs in parallel from Jenkins (which can be problematic when there are lot,...

> it's necessary for other approaches too, isn't it? Yes, we always have to look up the host handle from the WASI fd, regardless of the approach. But if we...

All the work has been merged to main. The only WASI function that remains to be implemented on Windows is `poll_oneoff`.

Hi, I'm not really familiar with zephyr and whether it is POSIX compliant or not. If it is, it should be a matter of adding the missing headers to [`platform_internal.h`](https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/core/shared/platform/zephyr/platform_internal.h)...

Hi @lucasAbadFr, > Zephyr [File System API](https://docs.zephyrproject.org/latest/services/file_system/index.html) is not POSIX compliant, so I think it's a bad idea to include posix_file.c. Also Zephyr is a RTOS so it doesn't necessarily...

Hi, thanks for the quick response. I get the following error when trying to compile with `--size-level=1` or `--size-level=2`: `LLVM ERROR: Only small, tiny and large code models are allowed...

Sorry, I should have been more clear. I meant is it expected that the AOT module fails to load when `size-level` is set to 3?

Also, is there any way to estimate how much the size of the AOT file would increase (relatively) changing the `size-level` from 3 to 0?

Thanks, that's good to know. I'm still a bit concerned that the AOT module fails to load when `size-level=3`, is there any possible explanation for this behaviour?

I'm still getting the same error `AOT module load failed: target address out of range.` I'll try to investigate further.