wip: update compiler to use miden-vm v0.18 #681
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements the necessary changes to migrate to the v0.18 release of the various VM crates we rely on.
NOTE: This cannot be merged until v0.18 is released and
miden-base
,miden-client
, andmiden-node
have migrated (and ideally also been released, but we could also pin to a git ref likenext
temporarily if need be). That should be some time next week I believe. Until then, any of our integration tests that depend on those crates will fail to compile.The main things that change here are:
account_component_metadata
field ofmiden_mast_package::Package
, and the addition of first-class custom section support (where the account component metadata is now stored).miden_assembly_syntax::ast::Instruction
variants related to MASM'spush
instruction, replacing them withPush(IntValue)
andPushWord(WordValue)
variants. This required changing a bunch of uses of the old variants in the codegen backend, which has been refactored a bit to avoid hardcoding whatInstruction
variant is used in all those places, instead centralizing it in the emitter.SyncHost
/AsyncHost
traits of the processor