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 8 pull requests #127819

Merged
merged 25 commits into from
Jul 16, 2024
Merged

Rollup of 8 pull requests #127819

merged 25 commits into from
Jul 16, 2024

Conversation

matthiaskrgr
Copy link
Member

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

Zalathar and others added 25 commits July 16, 2024 11:51
This makes it easier to see that the split point is always the index after the
found item, or the whole list if no stopping point was found.
this is redundant, so we can just delete it.
… impossible for visitor impls to look at these values
…, r=nnethercote

Fix the issue of invalid suggestion for a reference of iterator

Fixes rust-lang#127590
match lowering: Use an iterator to find `expand_until`

A small cleanup that I noticed while looking at rust-lang#127164.

This makes it easier to see that the split point is always the index after the found item, or the whole list if no stopping point was found.

r? `@Nadrieril`
…petrochenkov

Fix and enforce `unsafe_op_in_unsafe_fn` in compiler

In preparation for edition 2024, this PR previews the fallout of enabling the `unsafe_op_in_unsafe_fn` lint in the compiler, since it's defaulting to warn in the new edition (rust-lang#112038).

The major annoyance comes primarily from the `rustc_codegen_llvm` module, where there's a ton of unsafe calls. I tended to wrap individual calls to unsafe fns in `unsafe {}`, but there a handful of places I chose to just wrap several calls in an `unsafe {}` block just because it would've been excessive to wrap each call individually.

This doesn't enable the lint for the standard library, since I'm not totally certain what T-libs prefers w/ this lint.
delete #![allow(unsafe_op_in_unsafe_fn)] in teeos

deny unsafe_op_in_unsafe_fn for teeos
…jieyouxu

run-make-support: update gimli to 0.31.0

This version bump is required for the tests in rust-lang#126985 as suggested [here](rust-lang#126985 (comment)).

r​? tgross35
(^ that didn't work. cc `@tgross35)`

try-job: x86_64-msvc
try-job: x86_64-mingw
try-job: aarch64-apple
try-job: test-various
try-job: armhf-gnu
try-job: dist-x86_64-linux
…,nnethercote

Make ErrorGuaranteed discoverable outside types, consts, and lifetimes

types like `PatKind` could contain `ErrorGuaranteed`, but not return them via `tainted_by_errors` or `error_reported` (see rust-lang#127687 (comment)). Now this happens, but it's a bit fragile as you can see with the `TypeSuperVisitable for Ty` impl.

We will catch any problems around Ty, Region or Const at runtime with an assert, and everything using derives will not have such issues, as it will just invoke the `TypeVisitable for ErrorGuaranteed` impl
…enkov

Fix a bunch of sites that were walking instead of visiting, making it impossible for visitor impls to look at these values

This doesn't affects anything right now, but a `MutVisitor` impl could be surprised by this.

The reason this doesn't affect anything is that no one overrrides `visit_lifetime` or `visit_param_bounds` currently.
…ions, r=petrochenkov

Various ast validation simplifications

Changes pulled out of rust-lang#127524

These are needed to make ast validation a mutable visitor, as we can't keep immutable references to the AST around in that case. But I think they are simplifying things in general and can stand on their own
@rustbot rustbot added A-run-make Area: port run-make Makefiles to rmake.rs S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) 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. labels Jul 16, 2024
@rustbot rustbot added the rollup A PR which is a rollup label Jul 16, 2024
@matthiaskrgr
Copy link
Member Author

@bors r+ rollup=never p=8

@bors
Copy link
Contributor

bors commented Jul 16, 2024

📌 Commit ab4cc44 has been approved by matthiaskrgr

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 Jul 16, 2024
@bors
Copy link
Contributor

bors commented Jul 16, 2024

⌛ Testing commit ab4cc44 with merge 16b5690...

@bors
Copy link
Contributor

bors commented Jul 16, 2024

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing 16b5690 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Jul 16, 2024
@bors bors merged commit 16b5690 into rust-lang:master Jul 16, 2024
7 checks passed
@rustbot rustbot added this to the 1.81.0 milestone Jul 16, 2024
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#127669 Fix the issue of invalid suggestion for a reference of iter… 3ea2502f8eb5d5c95603b8aab4d320db11d76b8e (link)
#127707 match lowering: Use an iterator to find expand_until db72795de5b358bbb472d6a916f0fc4641364eed (link)
#127730 Fix and enforce unsafe_op_in_unsafe_fn in compiler e997a861b28f02f3d6a4f017476cd4a05ed0b47d (link)
#127789 delete #![allow(unsafe_op_in_unsafe_fn)] in teeos 0ccc3afad05034fafabbf4efca13e3c5cbee7411 (link)
#127805 run-make-support: update gimli to 0.31.0 8b0a504f3700f482d070fa9e260c924115d650a2 (link)
#127808 Make ErrorGuaranteed discoverable outside types, consts, an… 3ad9540e0eb09257d352bf3fc3506a0cdb342f94 (link)
#127817 Fix a bunch of sites that were walking instead of visiting,… 26ba88132fe3ebf6aa4e90c5ed3ac7f95b6dbd20 (link)
#127818 Various ast validation simplifications 3fe91f3eff7e9a536dabd0547bbe67c6168647d1 (link)

previous master: a91f7d72f1

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 (16b5690): 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

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

Binary size

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

Bootstrap: 700.14s -> 699.147s (-0.14%)
Artifact size: 328.63 MiB -> 328.64 MiB (0.00%)

@matthiaskrgr matthiaskrgr deleted the rollup-djdffkl branch September 1, 2024 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-run-make Area: port run-make Makefiles to rmake.rs 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-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) 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
Status: Done
Development

Successfully merging this pull request may close these issues.

10 participants