-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Wasmtime(gc): Support (ref.i31 (global.get $g))
const expressions
#8450
Wasmtime(gc): Support (ref.i31 (global.get $g))
const expressions
#8450
Conversation
01dabb7
to
574f70a
Compare
574f70a
to
53d8268
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.
Looks good to me, I think the organization worked out well here.
My main comment is that the unsafe
methods feel a little too unsafe and while I don't think there's a whole lot that can be done about that I still think it would be good to at least assert that Concrete
heap types are functions for now to avoid accidental confusion in the future.
We had something hacked together to support `(ref.i31 (i32.const N))`. It wasn't a long-term solution. This is the first time that we have to really deal with multi-instruction const expressions. This commit introduces a tiny interpreter to evaluate const expressions.
53d8268
to
19c2b23
Compare
This commit builds on the support added in bytecodealliance#8450 to extend our simple interpreter with support for the `extended-const` proposal to WebAssembly. This is required when updating the spec-test-submodule since `extended-const` was merged into the mainline specification and some proposals are starting to rebase on that.
This commit builds on the support added in #8450 to extend our simple interpreter with support for the `extended-const` proposal to WebAssembly. This is required when updating the spec-test-submodule since `extended-const` was merged into the mainline specification and some proposals are starting to rebase on that.
We had something hacked together to support
(ref.i31 (i32.const N))
. It wasn't a long-term solution. This is the first time that we have to really deal with multi-instruction const expressions.This commit introduces a tiny interpreter to evaluate const expressions.