-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Remove heaps from core Cranelift, push them into cranelift-wasm
#5386
Conversation
e534a6f
to
c06ac1c
Compare
c06ac1c
to
7027fd8
Compare
@cfallin I think this is ready for review! Sorry it got a bit big, probably best to go through commit by commit. |
7027fd8
to
643ffdd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great -- thanks for the careful and methodical work here and especially the attention to the testing! A few thoughts below but no showstoppers. r=me with comments addressed
...rch64/wasm/load_store_dynamic_kind_i32_index_0_guard_no_spectre_i32_access_0x1000_offset.wat
Outdated
Show resolved
Hide resolved
7c96347
to
a70c494
Compare
a70c494
to
5d7fc4a
Compare
Rather than using `heap_{load,store,addr}`.
These are now legalized in the `cranelift-wasm` frontend.
…essors.clif test
Heaps are not a thing in CLIF or the interpreter anymore
768be89
to
1cd66b5
Compare
This is a leftover from bytecodealliance#3302 where we used to inject a special `vmctx` struct if the test requested it. We've removed that capability in bytecodealliance#5386 but accidentally left this in, which caused some weird handling of these test invocations.
Still need to port filetests that use heaps over to a new thing, which I need to build and will land as a PR before this one.
Fixes #5283