Rollup of 13 pull requests #151023
Closed
Rollup of 13 pull requests #151023
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
Removes the double subject "it" in the safety documentation of `core::ptr::split_at_mut` for raw slice pointers, as it does not refer to anything. Reported-by: Johnathan Van Why <[email protected]>
Add .rmeta resolution for run-make/sysroot-crates-are-unstable test
After llvm/llvm-project#174174 it has profile info marking it cold.
I don't think it is necessary anymore. As I understand it from issue 39504 the original problem was that rustbuild changed a hardlink in the cargo build dir to point to copy in the sysroot while cargo may have hardlinked it to the original first. I don't think this happens anymore and as such this workaround is no longer necessary.
–- → – (extra ASCII minus after endash) Introduced in rust-lang#140463 (11627f0).
- Since UEFI has no threads, this should be safe. - Makes compiling remote-test-server simpler. Signed-off-by: Ayush Singh <[email protected]>
Dogfood `-Zno-embed-metadata` in the standard library This PR dogfoods the [`-Zno-embed-metadata`](rust-lang/cargo#15495) flag in the standard library. This removes the .rmeta portion out of the `libstd.so` file, thus reducing its filesize on disk. Notably, this reduces the amount of MiB that we ship to people who download the standard library. I think that the only way to find out what this breaks is to try to run full CI, and then try to land it on nightly :) r? @ghost
…vooeo Destabilise `target-spec-json` Per rust-lang/compiler-team#944: > Per rust-lang#71009, the ability to load target spec JSONs was stabilised accidentally. Within the team, we've always considered the format to be unstable and have changed it freely. This has been feasible as custom targets can only be used with core, like any other target, and so custom targets de-facto require nightly to be used (i.e. to build core manually or use Cargo's -Zbuild-std). > > Current build-std RFCs (rust-lang/rfcs#3873, rust-lang/rfcs#3874) propose a mechanism for building core on stable (at the request of Rust for Linux), which combined with a stable target-spec-json format, permit the current format to be used much more widely on stable toolchains. This would prevent us from improving the format - making it less tied to LLVM, switching to TOML, enabling keys in the spec to be stabilised individually, etc. > > De-stabilising the format gives us the opportunity to improve the format before it is too challenging to do so. Internal company toolchains and projects like Rust for Linux already use target-spec-json, but must use nightly at some point while doing so, so while it could be inconvenient for those users to destabilise this, it is hoped that an minimal alternative that we could choose to stabilise can be proposed relatively quickly.
std: move `errno` and related functions into `sys::io` Part of rust-lang#117276. Currently, `errno` and related functions like `decode_error_kind` are split across `sys::pal` and `sys::pal::os`. This PR moves all of them into a new module inside `sys::io`.
Remove legacy homu `try` and `auto` branch mentions ~~To be merged once we get rid of homu.~~ I think that we can merge this now.
…gross35 Add `f16` inline ASM support for s390x tracking issue: rust-lang#116909 cc rust-lang#125398 Support the `f16x8` type in inline assembly. Only with the `nnp-assist` feature are there any instructions that make use of this type. Based on the riscv implementation I now cast to `i16x8` when that feature is not enabled. As far as I'm aware there are no instructions operating on `f16` scalar values. Should we still add support for using them in inline assembly? r? @tgross35 cc @uweigand
…ouwer Move some checks from `check_doc_attrs` directly into `rustc_attr_parsing` Part of rust-lang#149865. I also used this opportunity to remove the `id_is_crate_root` method. Once this is merged, I think I'll try to see if we can remove `target_id` as well. r? @JonathanBrouwer
…ann,JonathanBrouwer Port `#[must_not_suspend]` to attribute parser Tracking issue: rust-lang#131229 r? @JonathanBrouwer
std: sys: net: uefi: Make TcpStream Send - Since UEFI has no threads, this should be safe. - Makes compiling remote-test-server simpler.
…, r=joboet core: ptr: split_at_mut: fix typo in safety doc Removes the double subject "it" in the safety documentation of `core::ptr::split_at_mut` for raw slice pointers, as it does not refer to anything. Reported-by: Johnathan Van Why <[email protected]>
…=durin42 Relax test expectation for @__llvm_profile_runtime_user After llvm/llvm-project#174174 it has profile info marking it cold.
Remove a workaround for a bug (take 2) I don't think it is necessary anymore. As I understand it from issue 39504 the original problem was that rustbuild changed a hardlink in the cargo build dir to point to copy in the sysroot while cargo may have hardlinked it to the original first. I don't think this happens anymore and as such this workaround is no longer necessary I can't reproduce the CI failure in rust-lang#122186 locally with `./x.py test library/core`. It is possible this got fixed by rust-lang#149273.
Fix typo in `MaybeUninit` docs –- → – (extra ASCII minus after endash) Introduced in rust-lang#140463 (11627f0).
Update books ## rust-lang/nomicon 2 commits in 5b3a9d084cbc64e54da87e3eec7c7faae0e48ba9..050c002a360fa45b701ea34feed7a860dc8a41bf 2026-01-10 15:05:01 UTC to 2026-01-09 23:34:23 UTC - Correct false typo fix in safe-unsafe-meaning.md (rust-lang/nomicon#518) - Fix grammar and typos in safe-unsafe-meaning.md (rust-lang/nomicon#517) ## rust-lang/reference 2 commits in 6363385ac4ebe1763f1e6fb2063c0b1db681a072..28b5a54419985f03db5294de5eede71b6665b594 2026-01-03 19:09:24 UTC to 2026-01-03 18:10:24 UTC - RISC-V Extensions update including 29 extensions to stabilize (rust-lang/reference#1987) - Update note about shebang removal in `include`d files (rust-lang/reference#2127) ## rust-lang/rust-by-example 1 commits in 2e02f22a10e7eeb758e6aba484f13d0f1988a3e5..8de6ff811315ac3a96ebe01d74057382e42ffdee 2026-01-06 00:16:33 UTC to 2026-01-06 00:16:33 UTC - Update comments on iterator behavior in closure examples (rust-lang/rust-by-example#1983)
rustbot
added
A-CI
Contributor
Author
|
@bors r+ rollup=never p=5 |
rust-bors
bot
added
S-waiting-on-bors
Contributor
This comment has been minimized.
This comment has been minimized.
rust-bors bot
pushed a commit
that referenced
this pull request
Jan 12, 2026
…uwer Rollup of 13 pull requests Successful merges: - #145343 (Dogfood `-Zno-embed-metadata` in the standard library) - #150151 (Destabilise `target-spec-json`) - #150723 (std: move `errno` and related functions into `sys::io`) - #150771 (Remove legacy homu `try` and `auto` branch mentions) - #150826 (Add `f16` inline ASM support for s390x) - #150934 (Move some checks from `check_doc_attrs` directly into `rustc_attr_parsing`) - #150943 (Port `#[must_not_suspend]` to attribute parser) - #150990 (std: sys: net: uefi: Make TcpStream Send) - #150995 (core: ptr: split_at_mut: fix typo in safety doc) - #150998 (Relax test expectation for @__llvm_profile_runtime_user) - #151002 (Remove a workaround for a bug (take 2)) - #151005 (Fix typo in `MaybeUninit` docs) - #151011 (Update books) r? @ghost
rust-bors
bot
added
S-waiting-on-review
Contributor
|
💔 Test for 8d04a9f failed: CI. Failed job:
|
Collaborator
|
A job failed! Check out the build log: (web) (plain enhanced) (plain) Click to see the possible cause of the failure (guessed by this bot) |
rustbot
removed
the
S-waiting-on-review
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
16 participants
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.
Successful merges:
-Zno-embed-metadatain the standard library #145343 (Dogfood-Zno-embed-metadatain the standard library)target-spec-json#150151 (Destabilisetarget-spec-json)errnoand related functions intosys::io#150723 (std: moveerrnoand related functions intosys::io)tryandautobranch mentions #150771 (Remove legacy homutryandautobranch mentions)f16inline ASM support for s390x #150826 (Addf16inline ASM support for s390x)check_doc_attrsdirectly intorustc_attr_parsing#150934 (Move some checks fromcheck_doc_attrsdirectly intorustc_attr_parsing)#[must_not_suspend]to attribute parser #150943 (Port#[must_not_suspend]to attribute parser)MaybeUninitdocs #151005 (Fix typo inMaybeUninitdocs)r? @ghost
Create a similar rollup