Skip to content

Rollup of 15 pull requests - #163086

Closed
Zalathar wants to merge 39 commits into
rust-lang:mainfrom
Zalathar:rollup-w9maqUj
Closed

Zalathar wants to merge 39 commits into
rust-lang:mainfrom
Zalathar:rollup-w9maqUj

Conversation

@Zalathar

Copy link
Copy Markdown
Member

Successful merges:

r? @ghost

Create a similar rollup

ywxt and others added 30 commits September 14, 2026 13:44
Co-authored-by: malezjaa <poreba.kris@gmail.com>
```
error[E0308]: mismatched types
  --> $DIR/ref-pat-suggestions.rs:29:13
   |
LL |         let &mut _a = 0;
   |             ^^^^^^^   - this expression has type `{integer}`
   |             |
   |             expected integer, found `&mut _`
   |
   = note:           expected type `{integer}`
           found mutable reference `&mut _`
help: to declare a mutable variable use
   |
LL -         let &mut _a = 0;
LL +         let mut _a = 0;
   |
```
- mention `-Zmacro-backtrace` only for non-local macros
- include span for local macro encompassing error
Use same wording as cargo does when `package.edition` is unspecified.

Do not suggest `--edition=future` on stable.
It's only used for `self.root_cx.root_def_id()`, but
`self.infcx.root_def_id` is also available.
Duplicated items cause lots of confusing knock down errors. This change side-steps some known ICEs, and reduces the verbosity of crates with duplicated types at the cost of not emitting every error that we could.

Update tests that no longer crash:

120873 -> `tests/ui/resolve/multiple_definitions_attribute_merging.rs`
          (already existing)
123690 -> `tests/ui/resolve/duplicated-enum-variant.rs`
155482 -> `tests/ui/resolve/duplicated-item-in-const-generics.rs`
	  Added two cases from the report that still ICE.
…hite

When error from local macro, include macro def span

- mention `-Zmacro-backtrace` only for non-local macros
- include span for local macro encompassing error
…anieu

add case mapping fast paths for Latin-1

Result:

Benchmark | Before (ns/iter) | After (ns/iter) | Improvement
-- | -- | -- | --
bench_ascii_mix_to_lowercase | 122,779.62 | 62,625.20 | 48.99%
bench_ascii_mix_to_uppercase | 140,644.43 | 62,216.00 | 55.76%
bench_non_ascii_char_to_lowercase | 178,361.80 | 62,815.57 | 64.78%
bench_non_ascii_char_to_uppercase | 215,988.75 | 62,073.67 | 71.26%
bench_non_latin1_char_to_lowercase | 296,788.33 | 293,113.17 | -
bench_non_latin1_char_to_uppercase | 348,730.00 | 347,126.50 | -
bench_ascii_char_to_lowercase | 65,546.00 | 62,120.53 | -
bench_ascii_char_to_uppercase | 65,532.87 | 62,126.94 | -

r? @Amanieu
…chenkov

Do not continue past `rustc_resolve` when encountering duplicated items

Duplicated items cause *lots* of confusing knock down errors. This change side-steps some known ICEs, and reduces the verbosity of crates with duplicated items at the cost of not emitting every error that we could.

Noticed just how problematic these can be while looking at rust-lang#160695, as `#[derive]`s are particularly prone to the kind of confusion these duplicates cause.

Fix rust-lang#120873, fix rust-lang#123690.

r? @petrochenkov
…l, r=lolbinarycat

rustdoc: account for nested parens and split text events in bare urls lint

Improve the `rustdoc::bare_urls` lint handling of underscores and parenthesis.

This re-does rust-lang#162381, but it has more test cases, and it handles nesting correctly.

r? @lolbinarycat

Fixes rust-lang#162345
…me-range-patterns, r=petrochenkov

Report runtime range endpoints for runtime values

Fixes rust-lang#131327
…rkaround, r=folkertdev

Use x30 register name with LLVM 23+

Closes rust-lang#148900

Thanks to llvm/llvm-project#167783, LLVM now recognizes the `x30`/`x29` register names.

r? @folkertdev
@rustbot rustbot added 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-clippy Relevant to the Clippy team. 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. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. labels Sep 21, 2026
@Zalathar

Copy link
Copy Markdown
Member Author

Rollup of everything not in #163071.

@bors r+ rollup=never p=5

@rust-bors

rust-bors Bot commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 693c0e8 has been approved by Zalathar

It is now in the queue for this repository.

@rust-bors rust-bors Bot 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 Sep 21, 2026
@rust-bors

This comment has been minimized.

rust-bors Bot pushed a commit that referenced this pull request Sep 21, 2026
Rollup of 15 pull requests

Successful merges:

 - #161051 (When error from local macro, include macro def span)
 - #162750 (add case mapping fast paths for Latin-1)
 - #162831 (Do not continue past `rustc_resolve` when encountering duplicated items)
 - #162835 (rustdoc: account for nested parens and split text events in bare urls lint)
 - #163044 (Report runtime range endpoints for runtime values)
 - #163062 (Use x30 register name with LLVM 23+)
 - #158102 (When compiling without a specified `--edition`, emit a note)
 - #162984 (Windows: don't error if `access_mode` is set on `OpenOptions`)
 - #163005 (Avoid unreachable integer underflow check in `CStr::count_bytes()`)
 - #163019 (Prepare for the introduction of forced keywords (`k#`))
 - #163020 (Dir: fix fallback impl for remove_dir)
 - #163047 (Use verbose suggestion for `mut binding` instead of `&mut binding`)
 - #163075 (Fix ArgAttributes mismatches in ABI UI tests for LoongArch64 and RiscV64)
 - #163079 (enable `f128` from `u64`/`i64` test)
 - #163082 (Remove `TypeChecker::root_cx`)
@rust-log-analyzer

Copy link
Copy Markdown
Collaborator

The job test-x86_64-gnu-aux failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)

@rust-bors rust-bors Bot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Sep 21, 2026
@rust-bors

rust-bors Bot commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

💔 Test for 1710120 failed: CI. Failed job:

@JonathanBrouwer

Copy link
Copy Markdown
Member

@bors try jobs=test-x86_64-gnu-aux

@rust-bors

This comment has been minimized.

rust-bors Bot pushed a commit that referenced this pull request Sep 21, 2026
Rollup of 15 pull requests


try-job: test-x86_64-gnu-aux
@Zalathar

Copy link
Copy Markdown
Member Author

The test failure in cargo looks like it should be real, but so far I have no idea what could be causing it.

@JonathanBrouwer

JonathanBrouwer commented Sep 21, 2026

Copy link
Copy Markdown
Member

I have no idea either, but I've seen weird race conditions causing things like this before so I could believe it being spurious

@rust-bors rust-bors Bot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Sep 21, 2026
@rust-bors

rust-bors Bot commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

💔 Test for d20acba failed: CI. Failed job:

@rust-log-analyzer

Copy link
Copy Markdown
Collaborator

The job test-x86_64-gnu-aux failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)

@rustbot rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 21, 2026
@rust-bors rust-bors Bot added the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 21, 2026
@rust-bors

rust-bors Bot commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

PR #158102, which is a member of this rollup, was unapproved.

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

Labels

A-compiletest Area: The compiletest test runner A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-run-make Area: port run-make Makefiles to rmake.rs A-testsuite Area: The testsuite used to check the correctness of rustc rollup A PR which is a rollup S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-clippy Relevant to the Clippy team. 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. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.