-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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 and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Miri subtree update #127317
Miri subtree update #127317
Conversation
…me attribute This prevents the calculated name from going out of sync with exported_symbols. It also avoids having to special case the panic_impl lang item.
Rustup To unblock rust-lang/miri#3688
Use the symbol_name query instead of trying to infer from the link_name attribute This prevents the calculated name from going out of sync with exported_symbols. It also avoids having to special case the panic_impl lang item. It also makes it easier to fix miri with rust-lang#127173.
Add syscall `dup()` for unix target Add support for `dup()` and `dup2()`. Fixes rust-lang#3454
Implement the `_mm256_zeroupper` and `_mm256_zeroall` intrinsics These two intrinsics were missing from the original implementation of the AVX intrinsics. Fortunately their implementation is trivial.
Automatic Rustup
…end-write, r=RalfJung TB: Refine protector end semantics Tree Borrows has protector end tag semantics, namely that protectors ending cause a [special implicit read](https://perso.crans.org/vanille/treebor/diff.0.html) on all locations protected by that protector that have actually been accessed. See also rust-lang#3067. While this is enough for ensuring protectors allow adding/reordering reads, it does not prove that one can reorder writes. For this, we need to make this stronger, by making this implicit read be a write in cases when there was a write to the location protected by that protector, i.e. if the permission is `Active`. There is a test that shows why this behavior is necessary, see `tests/fail/tree_borrows/protector-write-lazy.rs`.
The Miri subtree was changed cc @rust-lang/miri |
@bors r+ p=1 |
Miri subtree update r? `@ghost`
💔 Test failed - checks-actions |
Looks unrelated |
☀️ Test successful - checks-actions |
Finished benchmarking commit (c422581): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)Results (primary 1.7%, secondary -2.6%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResults (secondary -9.6%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 742.325s -> 721.419s (-2.82%) |
r? @ghost