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

Use a helper method to invoke VMFuncRef::array_call #9630

Merged
merged 3 commits into from
Nov 20, 2024

Conversation

alexcrichton
Copy link
Member

This is intended to encapsulate the usage of a native raw pointer and in the future act as a dispatch point for invoking Pulley instead of native code.

This is intended to encapsulate the usage of a native raw pointer and in
the future act as a dispatch point for invoking Pulley instead of native
code.
@alexcrichton alexcrichton requested a review from a team as a code owner November 20, 2024 15:56
@alexcrichton alexcrichton requested review from pchickey and removed request for a team November 20, 2024 15:56
@alexcrichton alexcrichton requested a review from a team as a code owner November 20, 2024 16:05
@github-actions github-actions bot added wasmtime:api Related to the API of the `wasmtime` crate itself wasmtime:c-api Issues pertaining to the C API. labels Nov 20, 2024
@alexcrichton alexcrichton added this pull request to the merge queue Nov 20, 2024
Merged via the queue into bytecodealliance:main with commit 8995bcc Nov 20, 2024
42 checks passed
@alexcrichton alexcrichton deleted the refactor-call-wasm branch November 20, 2024 18:50
alexcrichton added a commit to alexcrichton/wasmtime that referenced this pull request Nov 20, 2024
This pointer is technically not safe to be a function pointer because it
will get unloaded when the module is dropped. Additionally with Pulley
this isn't actually a native function pointer. This builds on bytecodealliance#9630 to
prepare for future integration with Pulley to ensure that the number of
locations that have to deal with bytecode-vs-native-code are minimized.
alexcrichton added a commit to alexcrichton/wasmtime that referenced this pull request Nov 20, 2024
This pointer is technically not safe to be a function pointer because it
will get unloaded when the module is dropped. Additionally with Pulley
this isn't actually a native function pointer. This builds on bytecodealliance#9630 to
prepare for future integration with Pulley to ensure that the number of
locations that have to deal with bytecode-vs-native-code are minimized.
github-merge-queue bot pushed a commit that referenced this pull request Nov 21, 2024
This pointer is technically not safe to be a function pointer because it
will get unloaded when the module is dropped. Additionally with Pulley
this isn't actually a native function pointer. This builds on #9630 to
prepare for future integration with Pulley to ensure that the number of
locations that have to deal with bytecode-vs-native-code are minimized.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wasmtime:api Related to the API of the `wasmtime` crate itself wasmtime:c-api Issues pertaining to the C API.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants