IRGen: Use indirect relative func-ptr for harvard archs #41995
Closed
Conversation
This file contains 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
Harvard architectures like WebAssembly cannot make direct relative function pointer because the referent function and the metadata are in different address spaces, and the relative offset between them is not representable. So we need to force such relative function pointers to always be indirect for those archs.
|
@swift-ci Please test |
|
preset=buildbot_incremental_linux_crosscompile_wasm |
|
@swift-ci please test macOS platform |
|
From our forum discussion, we are going to use absolute pointer unconditionally #42094 |
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.
Harvard architectures like WebAssembly cannot make direct relative function pointer because the referent function and the metadata are in different address spaces and the relative offset between them is not representable.
So we need to force such relative function pointers to always be indirect for those archs.
This change shouldn't affect other than WebAssembly, and Runtime changes will come in another PR
See also: https://forums.swift.org/t/wasm-support/16087/39