Conversation
…sl,ohos} In issue rust-lang#118053, the `loongarch64-unknown-linux-gnu` target needs indirection to access external data, and so do the `loongarch64-unknown-linux-musl` and `loongarch64-unknown-linux-ohos` targets.
llvm/llvm-project#91101 propagates range information across inlining, resulting in more metadata in this test. Tolerate the range metadata if it appears.
heuristic was: if it easily allows removing bangs entirely? worth it. if it requires more effort or just moves the bang? not.
Change orphan hint from "only" to "any uncovered type inside..." Fix rust-lang#128390
Setting up indirect access to external data for loongarch64-linux-{musl,ohos}
In issue rust-lang#118053, the `loongarch64-unknown-linux-gnu` target needs indirection to access external data, and so do the `loongarch64-unknown-linux-musl` and `loongarch64-unknown-linux-ohos` targets.
…n-compat, r=aDotInTheVoid rustdoc-JSON: Rename "object safe" to "dyn compatible" ~~Blocked: Sits atop rust-lang#131594. Only the last commit is relevant.~~ (rebased) Part of rust-lang#130852. r? aDotInTheVoid or rustdoc
cleanup canonical queries best reviewed commit by commit. adding `CanonicalQueryInput` to stop returning `defining_opaque_types` in query responses is the most involved change here. r? ``@compiler-errors``
llvm: Tolerate propagated range metadata llvm/llvm-project#91101 propagates range information across inlining, resulting in more metadata in this test. Tolerate the range metadata if it appears. ``@rustbot:`` label +llvm-main r? ``@durin42`` Please wait a moment before approving, putting the llvm-main tag on it to make sure it fixes the integration test.
…e-or, r=jieyouxu compiler: use `is_none_or` where it is clearly better heuristic was: if it easily allows removing bangs entirely? worth it. if it requires more effort or just moves the bang? not.
…youxu extract `expr_assign_expected_bool_error` moving diagnostics code out of the happy path makes it a lot easier to read imo
|
@bors r+ rollup=never p=7 |
|
☀️ Test successful - checks-actions |
|
📌 Perf builds for each rolled up PR:
previous master: 06d261daf6 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
|
Finished benchmarking commit (03983fb): 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.9%, secondary -0.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.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 780.529s -> 781.303s (0.10%) |
Successful merges:
is_none_orwhere it is clearly better #131815 (compiler: useis_none_orwhere it is clearly better)expr_assign_expected_bool_error#131822 (extractexpr_assign_expected_bool_error)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup