Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rollup of 6 pull requests #136534

Merged
merged 22 commits into from
Feb 4, 2025
Merged

Rollup of 6 pull requests #136534

merged 22 commits into from
Feb 4, 2025

Conversation

jhpratt
Copy link
Member

@jhpratt jhpratt commented Feb 4, 2025

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

pitaj and others added 22 commits February 1, 2025 13:34
…ing signed type

There was a macro parameter giving signed impls access to the
corresponding unsigned type, but not the other way around.

This will allow implementing methods converting in both directions.
- duplicates of crateresolve1 are used in a couple error-codes tests
- also fix the note in crateresolve1 to link to these other duplicates,
  now that E0523 has been merged into E0464
`rustc_middle` and `rustc_query_system` both have a file called
`dep_node.rs` with a big comment at the top, and the comments are very
similar. The one in `rustc_query_system` looks like the original, and
the one in `rustc_middle` is a copy with some improvements.

This commit removes the comment from `rustc_middle` and updates the one
in `rustc_query_system` to include the improvements. I did it this way
because `rustc_query_system` is the crate that defines `DepNode`, and so
seems like the right place for the comment.
The same comments are on the `DepNodeExt` trait and the single impl of
that trait, immediately below. This commit eliminates the duplication.
It has a single call site and removing it makes the code simpler.
Perhaps there were more uses at some point in the past?
The `field_name`/`field_ty` don't need to be parameters, they can be
hardcoded.
- Mention THIR.
- Removed mentions of non-existent READMEs.
I *think* this addresses what the `FIXME` comments are asking for.
add UnsafeCell direct access APIs

- Implementation for ACP: rust-lang/libs-team#521
- Tracking issue rust-lang#136327
…ieyouxu

Some `rustc_middle` cleanups

Small cleanups I found while looking closely at this code.

r? `@jieyouxu`
std::fs: further simplify dirent64 handling

Follow-up to rust-lang#134678.

r? `@tgross35`
Fix last compare-mode false negatives in tests

This PR is a continuation of rust-lang#136310 and fixes the last remaining cases of false negatives when running tests under a compare-mode.

With these normalizations, all the compare-mode failures in `next-solver` (and `polonius`) should now be real, actual differences in diagnostics.
…nsigned, r=dtolnay

Add `cast_signed` and `cast_unsigned` methods for `NonZero` types

Requested in rust-lang#125882 .

Note that this keeps the same names as the methods currently present on other
integer types. If we want to rename them, we can rename them all at the same
time.
…rieb

Add note about `FnPtr` trait being exposed as public bound
@rustbot rustbot added A-query-system Area: The rustc query system (https://rustc-dev-guide.rust-lang.org/query.html) O-unix Operating system: Unix-like 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 Feb 4, 2025
@jhpratt
Copy link
Member Author

jhpratt commented Feb 4, 2025

@bors r+ rollup=never p=5

@bors
Copy link
Contributor

bors commented Feb 4, 2025

📌 Commit af178aa 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 Feb 4, 2025
@bors
Copy link
Contributor

bors commented Feb 4, 2025

⌛ Testing commit af178aa with merge 01e4f19...

@bors
Copy link
Contributor

bors commented Feb 4, 2025

☀️ Test successful - checks-actions
Approved by: jhpratt
Pushing 01e4f19 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Feb 4, 2025
@bors bors merged commit 01e4f19 into rust-lang:master Feb 4, 2025
7 checks passed
@rustbot rustbot added this to the 1.86.0 milestone Feb 4, 2025
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#136398 add UnsafeCell direct access APIs 5f0171071ca9c22c95a9554a3c7050871d28e042 (link)
#136465 Some rustc_middle cleanups 2f82b78255f239eb90c7b1011fa2d168faf44f45 (link)
#136479 std::fs: further simplify dirent64 handling 3782e60e67a0eb9eea8cf33f71b80d3ffed75757 (link)
#136504 Fix last compare-mode false negatives in tests c076f6528f43578df220160afc87df60f5e6c513 (link)
#136511 Add cast_signed and cast_unsigned methods for NonZero a7ae234afad011924e826182e7acedcc744a11b7 (link)
#136518 Add note about FnPtr trait being exposed as public bound 81d0aa9a26e4b8c4583fac15f4bf9ee43aaf5265 (link)

previous master: 7b31983d55

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

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (01e4f19): 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)

Results (secondary -1.0%)

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.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-1.0% [-1.0%, -1.0%] 1
All ❌✅ (primary) - - 0

Cycles

Results (primary 4.2%)

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.

mean range count
Regressions ❌
(primary)
4.2% [4.2%, 4.2%] 1
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 4.2% [4.2%, 4.2%] 1

Binary size

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

Bootstrap: 778.8s -> 778.094s (-0.09%)
Artifact size: 328.88 MiB -> 328.84 MiB (-0.01%)

@jhpratt jhpratt deleted the rollup-dnz57dq branch February 5, 2025 05:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-query-system Area: The rustc query system (https://rustc-dev-guide.rust-lang.org/query.html) merged-by-bors This PR was explicitly merged by bors. O-unix Operating system: Unix-like 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.

10 participants