This repository was archived by the owner on Apr 28, 2025. It is now read-only.
Use core::arch::wasm functions rather than intrinsics#418
Merged
tgross35 merged 1 commit intorust-lang:masterfrom Jan 11, 2025
Merged
Use core::arch::wasm functions rather than intrinsics#418tgross35 merged 1 commit intorust-lang:masterfrom
core::arch::wasm functions rather than intrinsics#418tgross35 merged 1 commit intorust-lang:masterfrom
Conversation
These wasm functions are available in `core::arch::wasm32` since [1], so we can use them while avoiding the possibly-recursive `intrinsics::*` calls (in practice none of those should always lower to libcalls on wasm, but that is up to LLVM). Since these require an unstable feature, they are still gated under `unstable-intrinsics`. [1]: rust-lang/stdarch#1677
5b927ee to
117f685
Compare
This was referenced Jan 11, 2025
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
These wasm functions are available in
core::arch::wasm32since 1, so we can use them while avoiding the possibly-recursiveintrinsics::*calls (in practice none of those should always lower to libcalls on wasm, but that is up to LLVM).Since these require an unstable feature, they are still gated under
unstable-intrinsics.