This aligns the main error message a bit more with the phrasing in the
Edition Guide and provides a bit more information on the labels to
(hopefully!) aid in understanding.
(cherry picked from commit bdc6c4d07b)
[beta] backports
- Ensure that we don't try to access fields on a non-struct pattern type #135222
- Do not include GCC source code in source tarballs #135658
- Temporarily bring back `Rvalue::Len` #135709
- Add a couple of missing `ensure_sufficient_stacks` #136352
- Enable kernel sanitizers for aarch64-unknown-none-softfloat #135905
r? cuviper
We want kernels to be able to use this bare metal target, so
let's enable the sanitizers that kernels want to use.
(cherry picked from commit 6b06aa6192)
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 f854f34a50)
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`
Add `AsyncFn*` to `core` prelude
In https://github.com/rust-lang/rust/pull/132611 these got added to the `std` prelude only, which looks like an oversight.
r? libs-api
cc `@compiler-errors`
[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
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 aef640a613)
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 903cddb392)
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 45ef92731b)
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 cde58dd5f7)
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 93a19501c2)
[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
[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.
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 3d871b3ced)
