-
Notifications
You must be signed in to change notification settings - Fork 70
Latest wasi-libc
#719
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
Latest wasi-libc
#719
Conversation
18f28f0 to
b07e4a0
Compare
|
|
||
| WasmModule::~WasmModule() {} | ||
|
|
||
| void WasmModule::flush() {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This diff is very convoluted and hard to read. See here for the file and search for FAASM_HAS_WASM_MMAN.
The reason is that I wanted to conditionally compile the memory-management-related functions (similarly to what I do in include/wasm/WasmModule.h). However, I realised that the function definitions where not groupped in the same way that we declare them in the header file, so I re-arrange them to be so.
If preferred, I can just surgically conditionally compile the functions across this file and undo the re-ordering.
I am also aware that defining functions in the order we declare them is not something we enforce, but I still think is a nice-to-have.
346c274 to
e46740b
Compare
…t support PROT_EXEC
ad2ae27 to
6d6cbca
Compare
In this PR I bump the
cppandpythondependencie's to make our sysroot use the latest version ofwasi-libc.The changes here are just small fixes of problems that arised as a consequence of the merge. Most importantly, WASM's new command/reactor model defines as undefined behaviour calling twice the
_startsymbol of the same module instance. Equivalently, this means that WASM leaves the instance in an unusable state after execution. This helped catch a bug in threaded execution in faabric.See faasm/cpp#109