Miri subtree update by RalfJung · Pull Request #124727 · rust-lang/rust (original) (raw)
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 andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation7 Commits84 Checks6 Files changed
Conversation
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
[ Show hidden characters]({{ revealButtonHref }})
…sion-of-nodejs, r=RalfJung
bump actions/cache to v4
fixes rust-lang#3518.
Handle post-merge comments of AVX2 PR
file descriptors: make write take &mut self
Use the interpreted program's TZ variable in localtime_r
This requires a bit of wiring and a new dependency, but the tests should correctly pass now regardless of what the host's time zone is.
Fixes rust-lang/miri#3522
Don’t print Preparing a sysroot when -q/--quiet is passed
Resolves rust-lang#3530.
This also fixes a typo in cargo miri --help that I found while trying to run the --print-sysroot example.
Tree Borrows: first apply transition, then check protector with new 'initialized'
Move sched_getaffinity back to Linux
This reverts commit c1a3f8576ea12b0bed68ad3dedf4069ca3d9816f. The shim isn't actually useful for anything, and it is untested on FreeBSD. On Linux it exists solely because std and num_cpus are trying this before falling back to sysconf, but on FreeBSD that's not how they work, so there's no reason I can see to have this stub shim on FreeBSD.
… a missing foreign function
only show the 'basic API common for this target' message when this is a missing foreign function
Follow-up to rust-lang/miri#3558
These commits modify the Cargo.lock file. Unintentional changes to Cargo.lock can be introduced when switching branches and rebasing PRs.
If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.
The Miri subtree was changed
cc @rust-lang/miri
📌 Commit b5051c5 has been approved by RalfJung
It is now in the queue for this repository.
Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
and removed S-waiting-on-review
Status: Awaiting review from the assignee but also interested parties.
labels
fmease added a commit to fmease/rust that referenced this pull request
Miri subtree update
r? @ghost
bors added a commit to rust-lang-ci/rust that referenced this pull request
Rollup of 7 pull requests
Successful merges:
- rust-lang#122253 (Support Result<T, E> across FFI when niche optimization can be used)
- rust-lang#123892 (Document That
f16Andf128Hardware Support is Limited) - rust-lang#124458 (Implement lldb formattter for "clang encoded" enums (LLDB 18.1+))
- rust-lang#124459 (Stabilize exclusive_range_pattern)
- rust-lang#124711 (Migrate
run-make/doctests-runtoolto rmake) - rust-lang#124725 (Meta: Enable the brand new triagebot transfer command)
- rust-lang#124727 (Miri subtree update)
r? @ghost
@rustbot modify labels: rollup
bors added a commit to rust-lang-ci/rust that referenced this pull request
Rollup of 7 pull requests
Successful merges:
- rust-lang#122253 (Support Result<T, E> across FFI when niche optimization can be used)
- rust-lang#123892 (Document That
f16Andf128Hardware Support is Limited) - rust-lang#124458 (Implement lldb formattter for "clang encoded" enums (LLDB 18.1+))
- rust-lang#124459 (Stabilize exclusive_range_pattern)
- rust-lang#124711 (Migrate
run-make/doctests-runtoolto rmake) - rust-lang#124725 (Meta: Enable the brand new triagebot transfer command)
- rust-lang#124727 (Miri subtree update)
r? @ghost
@rustbot modify labels: rollup
This PR has been merged by accident, without the full test suite being run. It was my fault (#124631 got merged and it broke our CI). @RalfJung Could you please create a new PR with your branch against the latest version of origin/master? Thank you, and sorry for the mess.
Labels
This PR was explicitly merged by bors.
Status: Waiting on bors to run and complete tests. Bors will change the label on completion.