On AIX, PGO runtimes and ifunc support requires the named section linker feature which collects the name sections together and generates start/stop symbols for them.

This change adds the option to the default linker args for the target.

Coroutine variant of the closure / impl Fn 'static unsoundness family.
References in PR description.

ci-llvm include paths were leaking into debuginfo of `librustc_driver` via C/C++ compilation in rustc_llvm, causing non-determinism across
stage2 builds.

extend debug path remapping to the C/C++ build in rustc_llvm by converting RUSTC_DEBUGINFO_MAP into corresponding -fdebug-prefix-map flags and passing them through cc::Build.

Co-authored-by: Urgau <[email protected]>

This removes a separate call in the x86_64-gnu-llvm-21-3 job which runs
the ui-fulldeps a second time. ui-fulldeps is already running in the
first call (`../x.py --stage 1 test`) as it is a default test suite.

This was added in rust-lang#116009, but I
think that was a misunderstanding of the problem. The actual problem was
fixed in rust-lang#116932 where the actual
problem was the use of `&&`.

This doesn't really have much of an impact on CI time (only a couple
seconds) because all the tests are skipped with `ignored, up-to-date`.
I'm mainly doing this to clean up the script itself for clarity.

fix: more descriptive error message for enum to integer

Fixes rust-lang#151116
A  more descriptive error message when casting an enum to an Integer. Please review issue linked above.

generic_const_args: allow paths to non type consts

tracking issue: rust-lang#151972

Non type consts should be usable in the type system in `feature(generic_const_args)`. These are directly plugged into the constant evaluator, unlike type consts, which are attempted to be reasoned about by the type system.

Inherent associated constants are not supported at this time, due to complications around how generic arguments are represented for them (it's currently a mess). The mess is being cleaned up (e.g. rust-lang#154758), so instead of trying to hack support in before the refactoring is done, let's just wait to be able to implement it more cleanly.

r? @BoxyUwU

Adjust getMCSubtargetInfo signature for LLVM 23+

A recent [LLVM PR](llvm/llvm-project#195032) changed the signature of `getMCSubtargetInfo` to return a reference instead of a pointer. This adjusts uses of the function in `compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp` to account for the different signature.

…ohnTitor

add known-bug test for coroutine 'static-yields-non-'static unsoundness (rust-lang#144442)

Add a `known-bug` regression test for [rust-lang#144442 ("Unsoundness due to 'static coroutines that yield non-'static values").](rust-lang#144442)

Existing known-bug tests:
```
- tests/ui/closures/static-closures-with-nonstatic-return.rs
- tests/ui/implied-bounds/dyn-erasure-tait.rs
- tests/ui/implied-bounds/dyn-erasure-no-tait.rs
```

Verified in Darwin: running the compiled binary segfaults on current main, so the bug is still present.

…, r=JohnTitor

Move tests codegen

Hi, I have moved some tests into the codegen folder

move generalization test

The forth test of rust-lang/trait-system-refactor-initiative#191 (comment) isn't actually related to closure signature inference.

closes rust-lang/trait-system-refactor-initiative#191, which has already been fixed by rust-lang#155767

r? types