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.

Sign up for GitHub

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

Jump to bottom

Escape analysis for Wasm GC #9349

Open
Tracked by #9351
fitzgen opened this issue Oct 1, 2024 · 0 comments
Open
Tracked by #9351

Escape analysis for Wasm GC #9349

fitzgen opened this issue Oct 1, 2024 · 0 comments
Labels
cranelift:goal:optimize-speed Focus area: the speed of the code produced by Cranelift. performance wasmtime:ref-types Issues related to reference types and GC in Wasmtime

Comments

@fitzgen
Copy link
Member

fitzgen commented Oct 1, 2024

We could implement an escape analysis for Wasm GC types to figure out which allocations do not escape their stack frame. Then we can do unboxing/SROA, replacing a struct's fields or array elements with a set of local SSA values.
@fitzgen fitzgen added cranelift:goal:optimize-speed Focus area: the speed of the code produced by Cranelift. performance wasmtime:ref-types Issues related to reference types and GC in Wasmtime labels Oct 1, 2024
@fitzgen fitzgen mentioned this issue Oct 1, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cranelift:goal:optimize-speed Focus area: the speed of the code produced by Cranelift. performance wasmtime:ref-types Issues related to reference types and GC in Wasmtime
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fitzgen