merge master into next #486
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
This will be the last non-breaking release before v0.15 Updates the Changelog to include all changes (except for those related to testing/CI). Signed-off-by: Joe Richey <joerichey@google.com>
This switches to using the sparse index as reccomended by: https://crates.io/data-access#api Once merged, this should automatically release v0.14.12 (see #457). Signed-off-by: Joe Richey <joerichey@google.com>
Update data layout of test target for LLVM 18
This eliminates the call to unwrap which the compiler can't easily optimize out.
This eliminates a panic branch.
The last two commits introduced some shortcuts that are less obviously correct. Using unsafe is inherently risky, so we better be sure that the code is correct. The proof harnesses added in this patch can be used to proof that our implementation is correct for all inputs.
optimize `Step` impl for `VirtAddr`
We can't constify the public methods because const traits are not yet stable, but we can introduce private const methods that don't use traits. We'll use these internally in other const methods.
miscellaneous improvements
release v0.15.0
following #465 (review)
doc: added help on update_flags to get flags
Feat: add constructor for `InterruptStackFrameValue`
Starting with 0.15, the addition operator will no longer implicitly jump the gap in the address space. Instead, we can use Step::forward.
properly jump the address gap in CleanUp
The constant is Sealed::DEBUG_STR was also already exposed to users in its subtraits, but due to Sealed being unnamable reading DEBUG_STR was somewhat difficult. Moving the associated constants from the supertrait into the subtraits isn't a breaking change and makes it a bit more convenient to reference.
Signed-off-by: Martin Kröning <martin.kroening@eonerc.rwth-aachen.de>
Signed-off-by: Martin Kröning <martin.kroening@eonerc.rwth-aachen.de>
docs: add aliases for `in{,b,w,l}` and `out{,b,w,l}`
Signed-off-by: Martin Kröning <martin.kroening@eonerc.rwth-aachen.de>
Signed-off-by: Martin Kröning <martin.kroening@eonerc.rwth-aachen.de>
Signed-off-by: Martin Kröning <martin.kroening@eonerc.rwth-aachen.de>
Signed-off-by: Martin Kröning <martin.kroening@eonerc.rwth-aachen.de>
Signed-off-by: Martin Kröning <martin.kroening@eonerc.rwth-aachen.de>
ci: migrate away from unmaintained actions
Signed-off-by: Martin Kröning <martin.kroening@eonerc.rwth-aachen.de>
Signed-off-by: Martin Kröning <martin.kroening@eonerc.rwth-aachen.de>
Signed-off-by: Martin Kröning <martin.kroening@eonerc.rwth-aachen.de>
Signed-off-by: Martin Kröning <martin.kroening@eonerc.rwth-aachen.de>
Signed-off-by: Martin Kröning <martin.kroening@eonerc.rwth-aachen.de>
chore: migrate from legacy `rust-toolchain` to `rust-toolchain.toml`
test: replace `x86_64-bare-metal.json` with `x86_64-unknown-none`
fix and detect warnings
In d3b9c05, we switched our test framework to the built-in x86_64-unknown-none target. This required a `-Crelocation-model=static` flag to work with bootloader v0.9, which we set using a `build.rustflags` config key. In 2eb838d, we set a `RUSTFLAGS` env variable on CI to deny warnings. Unfortunately, the above two commits conflict because the `RUSTFLAGS` env variable takes precedence over the `build.rustflags` key. This commit fixes this by setting an explicit `RUSTFLAGS` value for the bootloader test job that contains both flags.
CI: Set `-Crelocation-model=static` in `RUSTFLAGS` for bootloader test job
silence warning about cast
A build on non-x86_64 platforms with the `instructions` feature enabled should not results in lots of inline assembly errors.
Only enable instructions on `x86_64`
* remove mention of doc_cfg feature `doc_cfg` has been superseded by `doc_auto_cfg`. * allow `cfg(kani)` Recently, rustc has started checking cfg expressions and so we have to tell it explicitly that cfg(kani) is allowed because it has no way of figuring that out itself.
phil-opp
approved these changes
May 22, 2024
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 PR syncs next with master.