Merge branch 'master' into next #356
Merged
Conversation
This file contains 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
Bump version to 0.14.8
make fields public
An overflow should not be possible since `VirtAddr` ise guarenteed to be a canoncial address, but it's better to be safe.
This ensures that we never return a non-canonical address from these methods, even if there is a bug in the address calculation. This is important because the `VirtAddr` type guarantees that all addresses are canoncial.
…le address Not just the invalid higher bits. We made the internal fields public in #340, but fortunately we didn't release this change yet, so this fix is still non-breaking.
Fix: `VirtAddrNotValid` and `PhysAddrNotValid` should contain the whole address
implement `core::iter::Step` for `VirtAddr` and `Page`
Fixed overflow bug in PageRangeInclusive
Add support for IA32_U_CET and IA32_S_CET, which are used for Control flow Execution Technology (CET) configuration. Signed-off-by: Jarkko Sakkinen <[email protected]>
User CET Register
Both `const_fn_fn_ptr_basics` and `const_fn_trait_bound` were stabilized in Rust relese 1.61. We can't immediately remove the `const_fn!` quite yet. 1.61 is not yet on stable, and even it were, removing them would increase our MSRV to 1.61 (which we may or may not want to do in a patch release). See also: #262 (comment) Signed-off-by: Joe Richey <[email protected]>
const_fn: Remove stabilized features
Signed-off-by: Joe Richey <[email protected]>
Signed-off-by: Joe Richey <[email protected]>
Signed-off-by: Joe Richey <[email protected]>
Signed-off-by: Joe Richey <[email protected]>
Use rustversion and remove const_fn!
Signed-off-by: Joe Richey <[email protected]>
Make `Entry::handler_addr()` a public method
Freax13
requested changes
Mar 26, 2022
Signed-off-by: Joe Richey <[email protected]>
phil-opp
approved these changes
Mar 26, 2022
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.
This is mostly just an additive change, based on the existing changes to
master.The only weird change is in
src/instructions/tables.rswhere we change theasm!flags. This was caused by a merge error in #338.I think we only have a few more breaking changes to implement before we should release 0.15
CheckedAddandCheckedSubtraits #293 (comment)All the other existing issues and PRs seem additive (except maybe #195).