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 wasmparser on the 3.0.0 update branch #75

Merged

Conversation

alexcrichton
Copy link
Member

This is a PR to update the jake/wasmtime branch which updates Wasmtime to 3.0.0. I believe the main blocker on that PR was a failing multi memory test which was due to the wasmparser used by wizer being too old. This updates wasmparser across the "great module linking removal" which necessitated deleting a lot more code in wizer related to module linking. To the best of my knowledge that's in line with the original intention of #65 so I'm hoping it's ok.

I'll note that I applied a mostly hack-and-slash approach to deleting module-linking code. I'm not intimiately familiar with everything deleted here.

Bring these up-to-date with the latest.
These dependencies are far behind the latest versions so this
fast-forwards them up to versions where larger changes are required.
This updates them enough to perform some minor rewrites here and there
but nothing major is changing.
This involved deleting quite a bit more module-linking related code in
`wizer`.
…mory

This commit further updates the `wasmparser` dependency across some
versions with minor renamings and structuring of the API. This pulls in
enough support to get the `multi_memory` test passing.
@alexcrichton
Copy link
Member Author

Also it seems prudent to further update various dependencies to their latest versions but for now I figure it's best to land the Wasmtime 3.0.0 update first and then try to go further from there.

@JakeChampion JakeChampion merged commit 6eacb7e into bytecodealliance:jake/wasmtime Apr 14, 2023
@alexcrichton alexcrichton deleted the update-wasmparser branch April 15, 2023 00:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants