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

Switch to new "user" stack maps and use i32 for GC refs in Wasmtime #9082

Merged
merged 1 commit into from
Aug 19, 2024

Conversation

fitzgen
Copy link
Member

@fitzgen fitzgen commented Aug 6, 2024

This moves Wasmtime over from the old, regalloc-based stack maps system to the new "user" stack maps system.

Removing the old regalloc-based stack maps system is left for follow-up work.

All tests are passing, and I've been running the table_ops fuzz target (which exercises GC refs, passing them between the host and Wasm, and their inline barriers) locally for a while with no more issues found (there was initially one issue found which was fixed in #9071).

@fitzgen fitzgen requested review from a team as code owners August 6, 2024 16:45
@fitzgen fitzgen requested review from elliottt and removed request for a team August 6, 2024 16:45
This moves Wasmtime over from the old, regalloc-based stack maps system to the
new "user" stack maps system.

Removing the old regalloc-based stack maps system is left for follow-up work.
@fitzgen fitzgen force-pushed the wasmtime-use-new-stack-maps branch from 1dedef5 to ac4bec2 Compare August 6, 2024 17:00
@github-actions github-actions bot added cranelift Issues related to the Cranelift code generator cranelift:area:machinst Issues related to instruction selection and the new MachInst backend. cranelift:wasm fuzzing Issues related to our fuzzing infrastructure wasmtime:api Related to the API of the `wasmtime` crate itself wasmtime:ref-types Issues related to reference types and GC in Wasmtime labels Aug 6, 2024
Copy link

github-actions bot commented Aug 6, 2024

Subscribe to Label Action

cc @fitzgen

This issue or pull request has been labeled: "cranelift", "cranelift:area:machinst", "cranelift:wasm", "fuzzing", "wasmtime:api", "wasmtime:ref-types"

Thus the following users have been cc'd because of the following labels:

  • fitzgen: fuzzing, wasmtime:ref-types

To subscribe or unsubscribe from this label, edit the .github/subscribe-to-label.json configuration file.

Learn more.

Copy link
Member

@elliottt elliottt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great! It's so cool to see the refs turn into stack slot usage in the disas tests :)

@fitzgen fitzgen added this pull request to the merge queue Aug 19, 2024
Merged via the queue into bytecodealliance:main with commit b2025ea Aug 19, 2024
37 checks passed
@fitzgen fitzgen deleted the wasmtime-use-new-stack-maps branch August 19, 2024 00:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cranelift:area:machinst Issues related to instruction selection and the new MachInst backend. cranelift:wasm cranelift Issues related to the Cranelift code generator fuzzing Issues related to our fuzzing infrastructure wasmtime:api Related to the API of the `wasmtime` crate itself wasmtime:ref-types Issues related to reference types and GC in Wasmtime
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants