Repository navigation
Conversation
Add `StackMap::slot_owner` (the push that made a stack slot live), `Machine` with the runtime's type sizes and record field offsets, `Try` with `ProcDisasm::tries`, `try_of` and `handler_exit`, and `runtime::Builtin` describing the functions the runtime registers itself. Fix `StackMap` following a `PopExceptionHandler` into the next section; it now follows `handler_exit`. All changes are additive, so this is a patch bump.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Release 0.2.1. All changes are additive, so this is a patch bump.
StackMap::slot_owner: the instruction whose push made a stack slot live before an instruction.Machine(X86,X64) withMachine::sizeandMachine::field_offset, matching the runtime'sTPSTypeRec.CalcSize/LoadTypeslayout.TryandProcDisasm::tries,try_ofandhandler_exit: eachtrya procedure installs, and where control continues after aPopExceptionHandler.StackMapfollowing aPopExceptionHandlerinto the next section; it followshandler_exit.runtime::Builtin: the side effects of each function the runtime registers itself (TPSExec.RegisterStandardProcs).See
CHANGELOG.mdfor details.Verification
cargo fmt --checkcargo clippy --all-targets -- -D warningscargo teston stable and on the MSRV (1.85): 54 passedRUSTDOCFLAGS="-D warnings" cargo doc --no-deps