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

Handle defined shared memories in dwarf processing #8750

Merged

Conversation

alexcrichton
Copy link
Member

This commit resolves an assert in the dwarf generating of core wasm modules when the module has a defined linear memory which is flagged shared. This is represented slightly differently in the VMContext than owned memories that aren't shared, and looks more like an imported memory. With support in #8740 it's now much easier to support this.

Closes #8652

This commit resolves an assert in the dwarf generating of core wasm
modules when the module has a defined linear memory which is flagged
`shared`. This is represented slightly differently in the `VMContext`
than owned memories that aren't `shared`, and looks more like an
imported memory. With support in bytecodealliance#8740 it's now much easier to support
this.

Closes bytecodealliance#8652
@fitzgen fitzgen added this pull request to the merge queue Jun 6, 2024
Merged via the queue into bytecodealliance:main with commit cdb5930 Jun 6, 2024
36 checks passed
@alexcrichton alexcrichton deleted the handle-defined-shared-memory branch June 6, 2024 13:42
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.

Cranelift: assertion left == right failed: the memory base pointer may be incorrect due to sharing memory
2 participants