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

Update wasm-tools crates to latest versions. #6394

Merged
merged 3 commits into from
May 17, 2023
Merged

Conversation

itsrainy
Copy link
Contributor

This included stubbing out unimplemented GC-related things and updating coredump generation to include the coredump spec changes.

This is to unblock #6385 (comment), where @pchickey is running into some duplicate dependencies issues.

This included stubbing out unimplemented GC-related things and
updating coredump generation to include the coredump spec changes.
@itsrainy itsrainy requested review from a team as code owners May 17, 2023 01:18
@itsrainy itsrainy requested review from fitzgen and removed request for a team May 17, 2023 01:18
@@ -194,6 +194,7 @@ impl Metadata {
saturating_float_to_int: _,
sign_extension: _,
floats: _,
gc: _,
Copy link
Member

Choose a reason for hiding this comment

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

Mind binding this as gc and asserting it's false down below (like memory_control)? We'll want to turn this on eventually and we won't want to forget to add handling here.

for f in bt.frames() {
modulenames.insert(f.module_name().unwrap_or("<unknown>"));
Copy link
Member

Choose a reason for hiding this comment

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

Should the modulenames set be deferred until the frame -> instance -> module mapping can be created? Otherwise there isn't anything pointing to the module names I think?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah I debated leaving that out, since it's essentially the same deal as instances. I'll remove it.

@github-actions github-actions bot added cranelift Issues related to the Cranelift code generator cranelift:wasm wasmtime:api Related to the API of the `wasmtime` crate itself labels May 17, 2023
@github-actions
Copy link

Subscribe to Label Action

cc @peterhuene

This issue or pull request has been labeled: "cranelift", "cranelift:wasm", "wasmtime:api"

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

  • peterhuene: wasmtime:api

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

Learn more.

@itsrainy
Copy link
Contributor Author

itsrainy commented May 17, 2023

@pchickey I'll defer to you on whether we want to merge this before or after your preview-2 support branch. I'm going to leave it for now so I don't hit you with any additional rebase burden.

@pchickey pchickey added this pull request to the merge queue May 17, 2023
Merged via the queue into main with commit 63ffbe2 May 17, 2023
@pchickey pchickey deleted the rainy/wasm-tools-update branch May 17, 2023 03:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cranelift:wasm cranelift Issues related to the Cranelift code generator wasmtime:api Related to the API of the `wasmtime` crate itself
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants