Skip to content

Conversation

@jhpratt
Copy link
Member

@jhpratt jhpratt commented Dec 30, 2025

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

bjoernager and others added 7 commits December 29, 2025 10:46
…dtolnay

Implement `TryFrom<char>` for `usize`.

Feature gate: `usize_try_from_char`.

This PR implements `TryFrom<char>` for `usize`.

`usize` is currently the only, unsigned, integral type to not implement `TryFrom<char>`. Technically, this conversion is trivial and can already be expressed with some indirection.

I think it useful to be able to describe this set of types with this interface.
…pratt

Mark set_times as unavailable for RTEMS target

This PR just updates one of the config switches to exclude `utimesat` for the RTEMS target.
This currently creates undefined reference errors when building the target.
With this fix applied it also needs a fix in libc (see rust-lang/libc#4875) which will hopefully be available in release 0.2.179.
mir_build: Remove several remnants of `#![feature(inline_const_pat)]`

This PR cleans up some THIR-related code that was only needed for inline `const { .. }` blocks in patterns. The `inline_const_pat` feature was removed in rust-lang#138492 due to implementation concerns.

I considered retaining the code for preserving `ExpandedConstant` for range endpoints, but ultimately decided to remove that too, because I found it very awkward to document an edge case that is currently not needed by any subsequent code.

With this PR, `is_const_pat_that_looks_like_binding` is the only function that meaningfully consumes `thir::PatKind::ExpandedConst`.
@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. rollup A PR which is a rollup labels Dec 30, 2025
@jhpratt
Copy link
Member Author

jhpratt commented Dec 30, 2025

@bors r+ rollup=never p=3

@bors
Copy link
Collaborator

bors commented Dec 30, 2025

📌 Commit 50e6224 has been approved by jhpratt

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Dec 30, 2025
@bors
Copy link
Collaborator

bors commented Dec 30, 2025

⌛ Testing commit 50e6224 with merge d465f99...

@bors
Copy link
Collaborator

bors commented Dec 30, 2025

☀️ Test successful - checks-actions
Approved by: jhpratt
Pushing d465f99 to main...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Dec 30, 2025
@bors bors merged commit d465f99 into rust-lang:main Dec 30, 2025
12 checks passed
@rustbot rustbot added this to the 1.94.0 milestone Dec 30, 2025
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#146792 Implement TryFrom<char> for usize. 403ce89403d193ab1b749903c75df833ad50ea6e (link)
#150484 Mark set_times as unavailable for RTEMS target 5bcdc290642e797eb54603438a9f7b0b6ef95b31 (link)
#150498 mir_build: Remove several remnants of `#![feature(inline_co… 1a779bcda2e8fdce2a7069189c65c1f227d0c1be (link)

previous master: d874dce125

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

@github-actions
Copy link
Contributor

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 d874dce (parent) -> d465f99 (this PR)

Test differences

Show 24 test diffs

24 doctest diffs were found. These are ignored, as they are noisy.

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard d465f990431b951f5b2d69aa499606db4b3ea359 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. x86_64-rust-for-linux: 2639.5s -> 3030.9s (+14.8%)
  2. x86_64-gnu-tools: 3202.5s -> 3615.7s (+12.9%)
  3. i686-gnu-2: 5375.0s -> 6065.7s (+12.8%)
  4. dist-x86_64-apple: 7895.2s -> 6961.9s (-11.8%)
  5. tidy: 170.0s -> 150.3s (-11.6%)
  6. pr-check-1: 1750.0s -> 1952.3s (+11.6%)
  7. x86_64-gnu-gcc: 3049.0s -> 3392.1s (+11.3%)
  8. x86_64-gnu-miri: 4583.7s -> 5083.9s (+10.9%)
  9. aarch64-gnu-debug: 3794.8s -> 4197.8s (+10.6%)
  10. dist-aarch64-apple: 7010.7s -> 7743.1s (+10.4%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (d465f99): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

This benchmark run did not return any relevant results for this metric.

Cycles

Results (secondary 2.6%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
5.0% [4.3%, 5.6%] 2
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-2.0% [-2.0%, -2.0%] 1
All ❌✅ (primary) - - 0

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 482.826s -> 482.641s (-0.04%)
Artifact size: 390.83 MiB -> 390.82 MiB (-0.00%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants