Conversation
Signed-off-by: tison <wander4096@gmail.com>
Fixes library linking issues where libgcc_s was incorrectly being linked instead of the appropriate LLVM runtime libraries for Hexagon targets. * Set llvm-libunwind as default for all hexagon targets in bootstrap * Exclude hexagon from automatic libgcc_s linking in unwind * Enable libunwind.a copying for hexagon targets * Remove manual library linking from hexagon target specification
If we convert the minimum length to `u64` up-front when creating `TestableCase::Slice`, we can avoid more conversions to `u64` later.
This was accidentally added to the prelude in 3f4dc1e.
Don't strip shebang in expr-ctxt `include!(…)` No longer strip shebang interpreter directives in files that were `include`d in expression (statement) contexts.
…=Mark-Simulacrum Add const default for OnceCell and OnceLock cc rust-lang#143894
…mulacrum miri: add -Zbinary-dep-depinfo to dependency builds Hopefully fixes rust-lang#149711 Cc ````@bjorn3````
…-Simulacrum Enable llvm-libunwind by default for Hexagon targets Fixes library linking issues where libgcc_s was incorrectly being linked instead of the appropriate LLVM runtime libraries for Hexagon targets. * Set llvm-libunwind as default for all hexagon targets in bootstrap * Exclude hexagon from automatic libgcc_s linking in unwind * Enable libunwind.a copying for hexagon targets * Remove manual library linking from hexagon target specification
fix docustring on fetch_or The documentation had the same example twice in a row, but I think this was the intended second example.
tests/ui/traits/fmt-pointer-trait.rs: Add HRTB fn pointer case Closes rust-lang#50280 which just **E-needs-test**. See rust-lang#50280 (comment) for a bisect of the fix. The issue description is quite vague, so in the test I am linking directly to the most descriptive comment rust-lang#50280 (comment).
Fix ICE (rust-lang#149980) for invalid EII in statement position Based on rust-lang#150159 Fixes rust-lang#149980
mir_build: Use the same length type for `TestableCase::Slice` and `TestKind::Len` If we convert the minimum length to `u64` up-front when creating `TestableCase::Slice`, we can avoid more conversions to `u64` later. There should be no change to compiler behaviour.
…reexport, r=GuillaumeGomez [rustdoc] Add missing close tags in extern crate reexports Fixes rust-lang#150176
change non-canonical clone impl to {*self}, fix some doc comments
…om-prelude, r=jdonszelmann Drop the From derive macro from the v1 prelude This was accidentally added to the prelude in 3f4dc1e. Fixes: rust-lang#150165 r? `````@jdonszelmann`````
|
@bors r+ rollup=never p=5 |
Rollup of 11 pull requests Successful merges: - #146377 (Don't strip shebang in expr-ctxt `include!(…)`) - #149812 (Add const default for OnceCell and OnceLock) - #149882 (miri: add -Zbinary-dep-depinfo to dependency builds) - #150009 (Enable llvm-libunwind by default for Hexagon targets) - #150035 (fix docustring on fetch_or) - #150082 (tests/ui/traits/fmt-pointer-trait.rs: Add HRTB fn pointer case) - #150160 (Fix ICE (#149980) for invalid EII in statement position) - #150184 (mir_build: Use the same length type for `TestableCase::Slice` and `TestKind::Len`) - #150185 ([rustdoc] Add missing close tags in extern crate reexports) - #150191 (change non-canonical clone impl to {*self}, fix some doc comments) - #150203 (Drop the From derive macro from the v1 prelude) r? `@ghost` `@rustbot` modify labels: rollup
|
looks like auto - dist-x86_64-linux is stuck, running since 4h 45m now :/ |
|
@bors retry r- |
|
@bors r+ |
|
☀️ Test successful - checks-actions |
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 f41f404 (parent) -> acfd264 (this PR) Test differencesShow 23 test diffsStage 1
Stage 2
Additionally, 15 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 acfd264f4df23b15cf27a15a85f76ed61977b48a --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: f41f40408d In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
|
Finished benchmarking commit (acfd264): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results (primary 2.5%, secondary 0.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -3.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary -0.1%, secondary -0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 479.466s -> 480.152s (0.14%) |
Successful merges:
include!(…)#146377 (Don't strip shebang in expr-ctxtinclude!(…))expected statement#149980) for invalid EII in statement position)TestableCase::SliceandTestKind::Len#150184 (mir_build: Use the same length type forTestableCase::SliceandTestKind::Len)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup