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

Merge with upstream #48

Merged
merged 2 commits into from
Jan 10, 2024
Merged

Merge with upstream #48

merged 2 commits into from
Jan 10, 2024

Conversation

dhil
Copy link
Member

@dhil dhil commented Jan 10, 2024

No description provided.

alexcrichton and others added 2 commits January 9, 2024 12:54
…liance#1365)

This commit is a follow-up to bytecodealliance#1260, bytecodealliance#1270, and bytecodealliance#1308. This is the next
step in the transition to updating how type information is encoded in
object files in core WebAssembly binaries when transforming them into a
component. The old format has been enabled by default since the 1.0.54
release of `wasm-tools` in late November. and has been supported since
the 1.0.51 release in early November.

Support has been preserved for continuing to emit the old format in case
any tooling accidentally hadn't updated but now feels like the right
time to remove the ability to emit the old format. The old format can
still be parsed if historical object files are in use and the hope is
that it's not too bad to leave that piece sticking around for awhile.
@dhil dhil merged commit 802554d into wasmfx:main Jan 10, 2024
6 checks passed
@dhil dhil deleted the wasmfx-merge branch January 10, 2024 12:03
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