Rollup of 6 pull requests - #160888
Conversation
Also clarify how the homu-ignore markers actually work.
`lib.rs` imports `DepNode`/`DepNodeIndex` even though it doesn't use them directly. And then `execution.rs` uses that one. Weird. This commit fixes things to be more normal.
It's a more sensible home than `mod job`.
The current name is very generic and the file is mostly about query vtables.
These four functions are all only used within `execution.rs`, so they no longer need `pub(crate)`. This is the first step toward eliminating `plumbing.rs`.
Because it now contains only things related to incremental. Also move two functions relating to incremental from `execution.rs` to `incremental.rs`.
It's a more sensible home than `lib.rs`.
It's a clearer name.
It's out of date.
…ieyouxu Add back homu-ignore markers around the PR template Besides reinstantiating the `homu-ignore` markers from rust-lang#126501, this PR also adds better clarification how the homu-ignore markers actually work; I've then also moved that section further down as it seems less important than the other parts of the PR template message. (We shouldn't forget that this is a *general PR template message*, not a LLM-policy-specific message.) The disclosure markers appear to have been accidentally removed together with the checkboxes in rust-lang#160785. In the future, if support for ignoring HTML comments in places such as markdown code blocks was added, the new description about how `<!-- homu-ignore:end -->`/`<!-- homu-ignore:start -->` can be used could be further simplified[^1], but I'd like to address the immediate issues first before considering any more involved improvements (there already *exist* [currently ~~6~~ 8] new PRs now that contain the whole template comment without `homu-ignore` markers). [^1]: actually it may always stay non-ideal given that HTML comments don't nest 🫠
…fonthey core: generalize `BorrowedCursor::ensure_init` Tracking issue: rust-lang#160476 This implements the future possibility left out in rust-lang#149749 (comment) and makes `ensure_init` generic over `Default`. I used specialisation to make sure the performance in the `u8` case stays equivalent to `memset` irrespective of how clever the optimiser happens to be. CC @joshtriplett as you've been working on this stuff recently. This also adds a public `write_default` method on `[MaybeUninit<T>]` that's doing the equivalent of `.write_init(|_| Default::default())`, but uses specialisation for integers. This uses the existing [tracking issue for `maybe_uninit_fill`](rust-lang#117428).
…mpl, r=Zalathar Overhaul `rustc_query_impl` The file/module structure is all over the place. In particular, `plumbing.rs` and `query_impl.rs` are pretty meaningless file names. r? @Zalathar
use `static` instead of `const` for derive(Debug) r? @ghost
Update books ## rust-lang/reference 9 commits in afdc77bab886d4455c11247cdd32391bfab636ae..82da570bafd9efed421bdbae0f8603ede8dd308b 2026-08-08 22:04:17 UTC to 2026-07-28 18:20:15 UTC - add c-variadic function definitions (rust-lang/reference#2177) - Update `no_mangle` to use the attribute template (rust-lang/reference#1904) - enums with fields: clarify that repr(C, int) is quite different from repr(int) (rust-lang/reference#2227) - aliasing rules also apply inside private fields (rust-lang/reference#2304) - attributes: do not explain syntax in rules (rust-lang/reference#2306) - Document prohibition on inner attribute macros (rust-lang/reference#2311) - Use authentication for linkcheck (rust-lang/reference#2319) - Stabilize passing 128-bit integers via vector registers with `asm!` on x86 (rust-lang/reference#2313) - Add a rule for attribute macro outline modules (rust-lang/reference#2310)
…rfonthey Implement <OnceCell,OnceLock>::new_init Tracking issues: rust-lang#159859 rust-lang#159860 I'm not sure If I was supposed to add any other tests apart from the doc tests.
|
@bors r+ p=5 |
This comment has been minimized.
This comment has been minimized.
|
📌 Perf builds for each rolled up PR:
previous master: 0e72e3266c In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
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 0e72e32 (parent) -> 0913b18 (this PR) Test differencesShow 114 test diffs114 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 0913b18e489ac1011b580e31fa5559654be12bfc --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 |
|
Finished benchmarking commit (0913b18): comparison URL. Overall result: ❌ regressions - 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 (primary -1.0%, secondary -0.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -0.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary 0.1%, secondary 0.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 454.011s -> 455.477s (0.32%) |
Successful merges:
BorrowedCursor::ensure_init#160432 (core: generalizeBorrowedCursor::ensure_init)rustc_query_impl#160843 (Overhaulrustc_query_impl)staticinstead ofconstfor derive(Debug) #160865 (usestaticinstead ofconstfor derive(Debug))r? @ghost
Create a similar rollup