Rollup of 15 pull requests#155837
Conversation
Also use the `\Device\NamedPipe\` directly instead of the symlink to it.
…tilities to observe, set, and create a Permissions struct with certain file attributes
The hyperlink to `std::io::Error` will not be valid when moved to `core::io`. There is also a typo which I might as well fix while I'm here.
Inconsistently referenced through `std::sys` and `std::io`. Choosing `std::io` as the canonical source to make migration to `core::io` cleaner.
This version no longer requires using big import libraries and instead uses raw-dylib.
unnamed_socket: do not introduce artifical short reads/writes
…e-short-ops Remove artificial short reads/writes from TCP sockets
Use windows-sys 0.61 in tests
Some architectures, such as RISC-V and LoongArch, lack support for native byte-sized atomic operations, so weak operations fallback to non-weak operations and are actually emulated by LL/SC loop, which never fail.
Use `AtomicUsize` instead of `AtomicBool` to test weak atomic for targets lacking byte-sized atomic
The previously pinned version of openssl-sys is not compatible with OpenSSL 4.0.x. - `openssl-sys`: 0.9.111 -> 0.9.114
This updates the rust-version file to 9836b06.
Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: rust-lang/rust@9836b06 Filtered ref: rust-lang/miri@9414676 Upstream diff: rust-lang/rust@e22c616...9836b06 This merge was created using https://github.com/rust-lang/josh-sync.
Automatic Rustup
bump openssl-sys to support OpenSSL 4.0.x
…xvar_epi64 Implement `_mm512_permutexvar_epi64` shim
…anilla
Suggest enclosing format string with `""` under special cases
This commit adds suggestions on enclosing format string with `""` when it falls into the following 3 cases: `{}`, `{:?}`, `{:#?}` as mentioned in rust-lang#155508.
Currently, this commit only recognizes the above 3 cases. I wonder if we should generalize this to more cases, for example, appying this suggestion to `Block`s with only 0 or 1 `Stmt`, such as `{:#x}`, `{:^10}`, `{abc}`.
…imulacrum Fix minor panic-unsoundness in CString::clone_into `CString` must always contain a null byte, calling `mem::take` on its inner allocation puts it in an invalid state (causing UB if e.g. it hits `CString::drop`) that can be observed if the allocator panics. Unfortunately, this solution allocates an intermediate 1-element `Box`. I'm not sure of a clean way to avoid that additional allocation; we could directly `realloc` if we want but it's tricky. Might be something we can do with `ManuallyDrop`. I do have a gnarly miri test for this that uses a panicky allocator, but I'm not sure where it would go. Happy to push it up if someone has a suggestion. Bug discovered by Rust Foundation Security using AI. I'm just helping with the patch as a member of wg-security-response. We do not believe this bug needs embargo, it is a soundness fix for hard-to-trigger unsoundness.
…rojections-issue-155365, r=ShoyuVanilla Suggest `.iter()` for shared projections Fixes rust-lang#155365.
…r=Kivooeo ssa_range_prop: use `if let` guards It is a bit cleaner this way r? @dianqk
…ejrs Cleanups to `AttributeExt` r? @mejrs - Makes some functions take `ast::Attribute` instead of `impl AttributeExt` - Remove `deprecation_note` from `AttributeExt`, since the two implementations are basically seperate
Mention `DEPRECATED_LLVM_INTRINSIC` lint for internal use Since `link_llvm_intrinsics` is an internal feature, having `deprecated_llvm_intrinsic` lint appearing in https://doc.rust-lang.org/nightly/rustc/lints/listing/allowed-by-default.html#deprecated-llvm-intrinsic without mentioning its internal nature is quite confusing to the end users. This PR improves the documentation of recently merged PR rust-lang#140763 that implemented `deprecated_llvm_intrinsic` lint by mentioning the internal nature of `deprecated_llvm_intrinsic` lint and `link_llvm_intrinsics` feature. Tracking issue of unstable `link_llvm_intrinsics` feature: rust-lang#29602
…rk-unstable, r=jhpratt,Urgau Remove the incomplete marker from `impl` restrictions Following the discussion on Zulip ([#gsoc > Idea: Implementing impl and mut restrictions @ 💬](https://rust-lang.zulipchat.com/#narrow/channel/421156-gsoc/topic/Idea.3A.20Implementing.20impl.20and.20mut.20restrictions/near/590562763)),this PR removes the incomplete marker from `#[feature(impl_restriction)]`. Tracking issue for restrictions: rust-lang#105077. r? @Urgau cc @jhpratt
Avoid improper spans when `...` or `..=` is recovered from non-ASCII - Fixes rust-lang#155799 Adjusting span endpoints by `BytePos(1)` is almost always bad news. In this case, the code assumed that it was skipping over a single ASCII character. But in the presence of parser recovery from other non-ASCII characters this resulted in an ICE due to bad string indexing when emitting suggestions.
…Brouwer Add default field values to diagnostic FormatArgs This type has a decent amount of unused fields (and I am planning to add more).
|
@bors r+ rollup=never p=5 |
This comment has been minimized.
This comment has been minimized.
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing d4f7856 (parent) -> ca9a134 (this PR) Test differencesShow 133 test diffsStage 1
Stage 2
Additionally, 127 doctest diffs were found. These are ignored, as they are noisy. Job group index
Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard ca9a134e0985765ded9cfdde4030a5df4db7e2bd --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
📌 Perf builds for each rolled up PR:
previous master: d4f7856569 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
|
Finished benchmarking commit (ca9a134): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (secondary 2.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 488.853s -> 488.117s (-0.15%) |
Successful merges:
pin!#153457 (prevent deref coercions inpin!)std::io::RawOsErrortocore::io#155574 (Movestd::io::RawOsErrortocore::io)""under special cases #155693 (Suggest enclosing format string with""under special cases).iter()for shared projections #155719 (Suggest.iter()for shared projections)if letguards #155779 (ssa_range_prop: useif letguards)AttributeExt#155789 (Cleanups toAttributeExt)DEPRECATED_LLVM_INTRINSIClint for internal use #155805 (MentionDEPRECATED_LLVM_INTRINSIClint for internal use)implrestrictions #155806 (Remove the incomplete marker fromimplrestrictions)...or..=is recovered from non-ASCII #155820 (Avoid improper spans when...or..=is recovered from non-ASCII)r? @ghost
Create a similar rollup