-
Notifications
You must be signed in to change notification settings - Fork 24
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
[2/3] Wasm CM support in frontend-wasm. Integration tests preparation (lazy IR compilation) #84
[2/3] Wasm CM support in frontend-wasm. Integration tests preparation (lazy IR compilation) #84
Conversation
4294a3e
to
b319fed
Compare
6a2c302
to
adcb3b7
Compare
b319fed
to
cd530d8
Compare
adcb3b7
to
c9a6033
Compare
26a9f7b
to
e244828
Compare
c9a6033
to
5950b30
Compare
e244828
to
fb8aca3
Compare
5950b30
to
a2b30fe
Compare
@@ -20,7 +20,7 @@ thiserror.workspace = true | |||
smallvec.workspace = true | |||
log.workspace = true | |||
anyhow.workspace = true | |||
wasmparser = "0.107" |
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.
Any reason to keep this pinned to the build version vs minor? The former would've still installed 0.118.1 with a cargo update
even though it mentions an older version. I don't have strong feelings either way, but I tend to pin to the minor version unless stability is a problem with a given crate.
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.
Minor would be enough here. I was unhappy with the breaking change below, so I was extra cautious.
#80
This PR is the second in the stacked PRs and should be merged after #82
This PR splits Wasm and IR compilations and unifies the compilation pipeline, making all tests go through the same IR passes.