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

support _initialize export as well as __wasm_call_ctors #1228

Merged
merged 1 commit into from
Oct 3, 2023

Conversation

dicej
Copy link
Collaborator

@dicej dicej commented Oct 3, 2023

Per WebAssembly/tool-conventions#203 and recent LLVM and wasi-libc changes, libraries may export an _initialize function instead of __wasm_call_ctors, and we should call whichever one we find. Note that we expect to find at most one of the two, and will return an error if both are found.

Per WebAssembly/tool-conventions#203 and recent LLVM and
wasi-libc changes, libraries may export an `_initialize` function instead of
`__wasm_call_ctors`, and we should call whichever one we find.  Note that we
expect to find at most one of the two, and will return an error if both are
found.

Signed-off-by: Joel Dice <joel.dice@fermyon.com>
@alexcrichton alexcrichton merged commit 60785ca into bytecodealliance:main Oct 3, 2023
15 checks passed
@dicej dicej deleted the call_initialize branch October 4, 2023 19:33
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

Successfully merging this pull request may close these issues.

None yet

2 participants