When `-Cstrip` was changed to use the bundled rust-objcopy instead of
/usr/bin/strip on OSX, strip-like arguments were preserved.

But strip and objcopy are, while being the same binary, different, they
have different defaults depending on which binary they are.
Notably, strip strips everything by default, and objcopy doesn't strip
anything by default.

Additionally, `-S` actually means `--strip-all`, so debuginfo stripped
everything and symbols didn't strip anything.

We now correctly pass `--strip-debug` and `--strip-all`.

This reverts commit 2316749.

This reverts commit f5577a8.

Prepare 1.85 beta release

r? `@ghost`

potential violations

(cherry picked from commit 045271c)

(cherry picked from commit 34edb21)

Co-authored-by: Rémy Rakic <remy.rakic+github@gmail.com>
(cherry picked from commit 13c7122)

…checking

(cherry picked from commit 197f6d8)

(cherry picked from commit 4a099b2)

(cherry picked from commit c55eefe)

[beta] stage0 bump and backports

- bump stage0 to 1.84.0
- Run borrowck tests on BIDs and emit tail-expr-drop-order lints for violations #134523

r? cuviper

This incorporates all the backwards-compatible changes for the 2024
Edition. There will also be a follow-on PR to land revisions to the new
chapter on async so it can be as ready as possible when officially
released with 1.85 and the 2024 Edition.

Additionally, there are a few other, non-backward-compatible, changes
(largely around `use<..>`) we can only land using the stable edition,
which we may or may not be able to land in 1.85 by using the beta
toolchain in the example code. Those may or may not be ported over,
depending on how that does or does not play with the infrastructure.

It has been a bit of a pain trying to keep the lints in sync across
the submodule repositories, so the just turns it off.

…cles leaking

The implementation is unsound when a partially consumed iterator has
some elements buffered in the front/back parts and cloning the Iterator
removes the capacity from the backing vec::IntoIter.

(cherry picked from commit 3d871b3)

(cherry picked from commit 1ed0ea4)

(cherry picked from commit 1b068a0)

(cherry picked from commit a40c659)

[beta] TRPL: incorporate all backward-compatible Edition changes

This incorporates all the backwards-compatible changes for the 2024 Edition. There will also be a follow-on PR to land revisions to the new chapter on async so it can be as ready as possible when officially released with 1.85 and the 2024 Edition.

Additionally, there are a few other, non-backward-compatible, changes (largely around `use<..>`) we can only land using the stable edition, which we may or may not be able to land in 1.85 by using the beta toolchain in the example code. Those may or may not be ported over, depending on how that does or does not play with the infrastructure.

This is identical to #135507 except that this targets `beta` instead of `master`, with the intent that these changes land in 1.85 and go out with the Edition release.

[beta] backports

- do not in-place-iterate over flatmap/flatten #135104
- Make sure to mark `IMPL_TRAIT_REDUNDANT_CAPTURES` as `Allow` in edition 2024 #135441
- Update to LLVM 19.1.7 #135484

r? cuviper

Backport rust-lang/rust-analyzer#18760

Creating a "trimmed DefID path" when no error is being emitted is an ICE (on purpose). If we create a trimmed path for a lint that is then silenced before being emitted causes a known ICE. This side-steps the issue by always using `with_no_trimmed_path!`.

This was verified to fix https://github.com/quinn-rs/quinn/, but couldn't write a repro case for the test suite.

Fix #135289.

(cherry picked from commit 93a1950)

(cherry picked from commit 7d80617)

There is a chance that these tools are being installed from an external LLVM
and we have no control over them. If any of these tools use symlinks, they will
fail during tarball distribution. This change makes copying process to resolve
symlinks just before placing them into the destination path.

Signed-off-by: onur-ozkan <work@onurozkan.dev>
(cherry picked from commit cde58dd)

(cherry picked from commit ebbcfd4)

(cherry picked from commit 94bf8f0)

(cherry picked from commit 0910173)

…tions with dummy spans instead of dropping them entirely

Revert most of #133194 (except the test and the comment fixes). Then refix
not emitting locations at all when the correct location discriminator value
exceeds LLVM's capacity.

(cherry picked from commit 45ef927)

Previously, bootstrap was using `Config::last_modified_commit` unconditionally to figure
the commit has to download precompiled rustc artifact from CI, which was leading builds to
fail on tarball sources as `Config::last_modified_commit` requires `git` to be present in the project
source. This change makes bootstrap to call `Config::last_modified_commit` only when it's running on
git-managed source and read `git-commit-hash` file otherwise.

Signed-off-by: onur-ozkan <work@onurozkan.dev>
(cherry picked from commit 903cddb)

(cherry picked from commit fed5f98)

The size of this struct depends on the alignment of `u128`, for example
powerpc64le and s390x have align-8 and end up with only 280 bytes. Our
64-bit tier-1 arches are the same though, so let's just assert on those.

(cherry picked from commit aef640a)

- Improve the discussion of `unsafe` blocks within `unsafe` functions.
- Fix formatting in Appendix A

[beta] backports

- Always force non-trimming of path in `unreachable_patterns` lint #135310
- Add Profile Override for Non-Git Sources #135433
- resolve symlinks of LLVM tool binaries before copying them #135585
- add cache to `AmbiguityCausesVisitor` #135618
- When LLVM's location discriminator value limit is exceeded, emit locations with dummy spans instead of dropping them entirely #135643
- make it possible to use ci-rustc on tarball sources #135722
- Remove test panic from File::open #135837
- Only assert the `Parser` size on specific arches #135855
- [beta] TRPL: more backward-compatible Edition changes #135843

r? cuviper

…-errors

Add `AsyncFn*` to `core` prelude

In #132611 these got added to the `std` prelude only, which looks like an oversight.

r? libs-api
cc `@compiler-errors`

…4, r=ytmimi

Disable `overflow_delimited_expr` in edition 2024

This reverts the style guide changes and sets the default to "false" in rustfmt for style edition 2024.

r? `@ytmimi`

cc `@rust-lang/style` `@rust-lang/rustfmt`

[beta-1.85] backports

* [Add `AsyncFn*` to `core` prelude](#135852)
* [Disable `overflow_delimited_expr` in edition 2024](#136312)
* [Disable some incorrect rust-analyzer diagnostics on beta](#136236)
    * [fix: Fix #[rustc_deprecated_safe_2024]](rust-lang/rust-analyzer#19044)
    * [fix: Fix a bug where enum variants were not considered properly in type ns resolution](rust-lang/rust-analyzer#18976)
* Update edition-guide
    * [Add alternatives for static-mut-refs](rust-lang/edition-guide#354)
    * [Remove rustfmt-overflow-delimited-expr](rust-lang/edition-guide#357)

…e in diagnostic

Fix #135209.

(cherry picked from commit 5f04f98)

(cherry picked from commit d44f021)

(cherry picked from commit 592f2c9)

The licensing story is unclear, it makes the archive much larger, and we should not need it for building anything in the tarballs (yet).

(cherry picked from commit f854f34)

…wjasper"

This reverts commit e108481, reversing
changes made to 303e8bd.

(cherry picked from commit ca1c17c)