openmp: add basic WAMR support for OpenMP #812
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4876b26 to
47afe2c
Compare
0f75614 to
fc486ad
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WARNING: probably our OpenMP errors are due to the fact that we do not enable WASM's atomics, and we may be running into a race condition when multiple threads operate on the same WASM module.
WAVM seems to be happy with this, but WAMR does not allow threads to share a module's memory unless the module has been compiled with the
--shared-memoryflag, which requires buildingwasi-libcand the toolchain withatomicsandbulk-memory.https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/doc/embed_wamr.md#execute-wasm-functions-in-multiple-threads