Skip to content

Automated pull from upstream HEAD#2239

Closed
ferrocene-automations[bot] wants to merge 689 commits intomainfrom
automation/pull-upstream-HEAD/mscy1uah
Closed

Automated pull from upstream HEAD#2239
ferrocene-automations[bot] wants to merge 689 commits intomainfrom
automation/pull-upstream-HEAD/mscy1uah

Conversation

@ferrocene-automations
Copy link
Copy Markdown

⚠️ The automation reported these warnings: ⚠️

  • There are merge conflicts in this PR. Merge conflict markers have been committed.

This PR pulls the following changes from the upstream repository:

JonathanBrouwer and others added 30 commits March 20, 2026 13:24
Fix typos and markdown errors

This PR fixes some typos and markdown errors I found while writing rust-lang/rust#153697.

I've split it out to reduce the size of that PR.
…athanBrouwer

refactor(attribute parser): move check_custom_mir to attribute parser

Part of rust-lang/rust#153101

r? @JonathanBrouwer
Auto generate trait name from first method.

Input:

```rust
impl S$0 {
    fn foo() {}
}
```

Old output:

```rust
trait NewTrait {
    fn foo();
}

impl NewTrait for S {
    fn foo() {}
}
```

This PR output:

```rust
trait Foo {
    fn foo();
}

impl Foo for S {
    fn foo() {}
}
```
…-from-impl

Add auto trait name for generate_trait_from_impl
…uwer

Rollup of 5 pull requests

Successful merges:

 - rust-lang/rust#154103 (coretests: Expand ieee754 parsing and printing tests to f16)
 - rust-lang/rust#152669 (rustc_public: add `vtable_entries()` to `TraitRef`)
 - rust-lang/rust#153776 (Remove redundant `is_dyn_thread_safe` checks)
 - rust-lang/rust#154121 (Fix typos and markdown errors)
 - rust-lang/rust#154126 (refactor(attribute parser): move check_custom_mir to attribute parser)
…(#16667)

Pull-requests get a warning because of

[RUSTSEC-2026-0007](https://rustsec.org/advisories/RUSTSEC-2026-0007.html).
Bumping `bytes` will silence the warning.

changelog: none

r? flip1995
Guard patterns: lowering to THIR

This pr implements lowering of guard patterns to THIR

r? @Nadrieril

cc @max-niederman

Tracking issue: rust-lang/rust#129967
…hanBrouwer

refactor - moving `check_stability` check to `parse_stability`

This PR is part of issue rust-lang/rust#153101 and by extension this rust-lang/rust#131229 as well

r? @JonathanBrouwer
llvm: Update `reliable_f128` configuration for LLVM22 on Sparc

LLVM22 should have resolved issues with the `f128` ABI, meaning we can now set `cfg(target_has_reliable_f128)` on the platform.

Link: llvm/llvm-project@3e16aef
vec::Drain::fill: avoid reference to uninitialized memory

`range_slice` points to memory that is not initialized (e.g. it might be dropped `Box`/`String`). Let's avoid that and instead use an index-based loop.
test copy_specializes_from_vecdeque: reduce iteration count for Miri

This test currently takes >20s and that doesn't really seem worth it.
These methods are just wrappers around the intrinsics.
Stash parse errors when pasing rtn that doesn't use `(..)`.
Emit single error on `Foo::bar(qux)` that looks like rtn in incorrect position and suggest `Foo::bar(..)`.
```
error: return type notation not allowed in this position yet
  --> $DIR/let-binding-init-expr-as-ty.rs:18:10
   |
LL | struct K(S::new(()));
   |          ^^^^^^^^^^
   |
help: furthermore, argument types not allowed with return type notation
   |
LL - struct K(S::new(()));
LL + struct K(S::new(..));
   |
```
On incorrect rtn in let binding type for an existing inherent associated function, suggest `:` -> `=` to turn the "type" into a call expression.
```
error: expected type, found associated function call
  --> $DIR/let-binding-init-expr-as-ty.rs:29:12
   |
LL |     let x: S::new(());
   |            ^^^^^^^^^^
   |
help: use `=` if you meant to assign
   |
LL -     let x: S::new(());
LL +     let x = S::new(());
   |
```
This improves startup performance by 16%, shown by an optimized
hello-world program. glibc's `pthread_getattr_np` performs expensive
syscalls when reading `/proc/self/maps`. That is all wasted with
`panic = immediate-abort` active because `init()` immediately discards
the return value from `install_main_guard()`. A similar improvement can
be seen in environments that don't have `/proc`. This change is safe
because the immediately succeeding comment says that we rely on Linux's
"own stack-guard mechanism".
Replace direct usage of make with syntax factory and migrate assist to syntaxEditor
JonathanBrouwer and others added 5 commits March 24, 2026 10:54
fix/extend some mir-opt comments

Looks like CopyProp was refactored without updating that comment.

And for GVN, I think this is what you had in mind @cjgillot but would be great if you could have a look.
…thanBrouwer

document some functions on AttributeExt

r? @jyn514
…uwer

Rollup of 4 pull requests

Successful merges:

 - rust-lang/rust#153434 (Use a safe `BucketIndex` abstraction in `VecCache`)
 - rust-lang/rust#154133 (Defer codegen for the VaList Drop impl to actual uses)
 - rust-lang/rust#154297 (fix/extend some mir-opt comments)
 - rust-lang/rust#154299 (document some functions on AttributeExt)
This commit is generated by `ferrocene/tools/pull-upstream/pull.sh`.
The list of excluded files is defined in `.gitattributes`.
@ferrocene-automations ferrocene-automations Bot added automation Issue or PR created by an automation backport:never PR that should never be backported labels Mar 24, 2026
@Hoverbear
Copy link
Copy Markdown
Member

bors try

bors-ferrocene Bot added a commit that referenced this pull request Mar 24, 2026
Comment thread tests/ui/const-generics/early/invalid-const-arguments.rs
@bors-ferrocene
Copy link
Copy Markdown
Contributor

try

Build failed:

@Hoverbear
Copy link
Copy Markdown
Member

bors try

bors-ferrocene Bot added a commit that referenced this pull request Mar 24, 2026
@bors-ferrocene
Copy link
Copy Markdown
Contributor

try

Build failed:

@jyn514
Copy link
Copy Markdown
Contributor

jyn514 commented Mar 25, 2026

[ui] tests/ui/delegation/bad-resolve.rs ... F

well that's odd

@jyn514 jyn514 added the waiting-on-author If this PR was opened by an automation, the "author" is the assignee. label Mar 25, 2026
@jyn514
Copy link
Copy Markdown
Contributor

jyn514 commented Mar 25, 2026

wrote up a bunch of improved diagnostics in rust-lang/rust#154387 but didn't fix the actual problem. i believe this is an upstream issue but as a workaround i'm going to add some short-circuiting if delegation is enabled and there's been any errors.

@Hoverbear
Copy link
Copy Markdown
Member

I see a conflict, will replay it in the morning

@jyn514
Copy link
Copy Markdown
Contributor

jyn514 commented Mar 27, 2026

upstream fix is rust-lang/rust#154368

@Hoverbear Hoverbear closed this Mar 27, 2026
@tshepang tshepang deleted the automation/pull-upstream-HEAD/mscy1uah branch March 27, 2026 19:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automation Issue or PR created by an automation backport:never PR that should never be backported waiting-on-author If this PR was opened by an automation, the "author" is the assignee.

Projects

None yet

Development

Successfully merging this pull request may close these issues.