Avoid illegal function pointer operation for async funcs #35220
Closed
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.
When compiling Concurrency module targeting wasm32, it fails with
Function addresses with offsets not supported
.It's a limitation of wasm32 for security reason. In wasm32, function and data address spaces are separated, so additive operation to function address as data pointer is invalid. Therefore if it's statically known to be an additive operation to function address, LLVM fails with the above error.
As far as I understand, if function pointer is a direct pointer to a function, it could not be an async function pointer. So this PR changes to emit undefs instead of offset operations.
I'm not familiar with this area, so I would appreciate it if you could tell me if I'm doing in wrong way.
CC: @nate-chandler