-
Notifications
You must be signed in to change notification settings - Fork 1
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
Linking tags #215
Linking tags #215
Conversation
I haven't implemented the proper runtime representation of tags in the baseline implementation yet. I am planning to defer that to a separate patch. |
This patch implements support for importing and exporting tags in the virtual machine. As a consequence tags are now unique to their origin instance, meaning that two different instantiations of the same module yields distinct tags. The runtime representation of a tag has changed from an `u32` to a `usize` (or native pointer). The identity of a tag is given by its address in the vmcontext. Resolves wasmfx#25.
d9b0343
to
816af74
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 generally seems to be in good shape, mostly some questions about tag-related types.
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 all looks good now.
This patch updates the README to reflect the recent changes to the CLI. I think the following bullet point in the limitations subsection is outdated: > - Only a single module can be executed. In particular, providing additional > modules using the `--preload` option of `wasmtime` can lead to unexpected > behavior. I think this should work after the proper tags patch #215. Though, I haven't tested it yet, so I will leave it be for now.
This patch implements support for importing and exporting tags in the virtual machine. As a consequence tags are now unique to their origin instance, meaning that two different instantiations of the same module yields distinct tags.
The runtime representation of a tag has changed from an
u32
to ausize
(or native pointer). The identity of a tag is given by its address in the vmcontext.Resolves #25.