| Age | Commit message (Collapse) | Author | Lines |
|---|
|
[stable] Prepare Rust 1.77.2
See https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html
|
|
|
|
|
|
|
|
Errors started showing up, and I read somewhere that this might be
because of old ninja versions. This ninja version is indeed *ancient*.
```
multiple outputs aren't (yet?) supported by depslog; bring this up on the mailing list if it affects you
```
|
|
|
|
|
|
[stable-1.77] cargo backport
1 commits in 3fe68eabf93cbf3772bbcad09a9206c783e2de3f..e52e360061cacbbeac79f7f1215a7a90b6f08442
2024-02-29 00:16:03 +0000 to 2024-03-26 17:54:36 +0000
- [stable-1.77] Do not strip debuginfo by default for MSVC (rust-lang/cargo#13654)
r? ghost
|
|
|
|
|
|
|
|
[stable] 1.77.0 release
https://forge.rust-lang.org/release/process.html#promote-branches-t-3-days-monday
r? `@Mark-Simulacrum`
|
|
|
|
|
|
[beta] Clippy backports
Backports included in this PR:
- https://github.com/rust-lang/rust-clippy/pull/12276 Fixing the lint on some platforms before hitting stable
- https://github.com/rust-lang/rust-clippy/pull/12405 Respect MSRV before hitting stable
- https://github.com/rust-lang/rust-clippy/pull/12266 Fixing an (unlikely) ICE
- https://github.com/rust-lang/rust-clippy/pull/12177 Fixing FPs before hitting stable
Each backport on its own might not warrant a backport, but the collection of those are nice QoL fixes for Clippy users, before those bugs hit stable.
All of those commits are already on `master`.
r? `@Mark-Simulacrum`
|
|
[beta] backports
- AST validation: Improve handling of inherent impls nested within functions and anon consts #122004
- Downgrade const eval dangling ptr in final to future incompat lint #122204
r? cuviper
|
|
(cherry picked from commit ae374cf04a30eac81de24c4fbdfb4d1c7f4f34e4)
|
|
lint.
(cherry picked from commit 6ca46daded8320dffe437b9008c2b353563af0a5)
|
|
that were expecting the hard error for it.
I attempted to do this in a manner that preserved the line numbers to reduce the
review effort on the resulting diff, but we still have to deal with the
ramifications of how a future-incompat lint behaves compared to a hard-error (in
terms of its impact on the diagnostic output).
(cherry picked from commit 1c3424bfc1354db47fd3901cb1b76c22fbe33392)
|
|
(cherry picked from commit f86b46a9cc0dadaee69ca4e4a911ce122db17b24)
|
|
to address issue 121610.
(cherry picked from commit a8549b4152566d8fbd34c097236df1db3d9afd3c)
|
|
and anon consts
(cherry picked from commit 7d428db605d305198481b2201f46f5f91d5f8369)
|
|
|
|
|
|
|
|
|
|
`os_local` impl of `thread_local` — regardless of whether it is const and
unlike other implementations — includes an `fn __init(): EXPR`.
Existing implementation of the lint checked for the presence of said
function and whether the expr can be made const. Because for `os_local`
we always have an `__init()`, it triggers for const implementations.
The solution is to check whether the `__init()` function is already const.
If it is `const`, there is nothing to do. Otherwise, we verify that we can
make it const.
Co-authored-by: Alejandra González <blyxyas@gmail.com>
|
|
[beta] backports
- Improve wording of `static_mut_ref` #121034
- Solaris linker does not support --strip-debug #121399
r? cuviper
|
|
Fixes #121381
(cherry picked from commit a17211b05c883eaeb4057f0a9207947bcbcc3688)
|
|
Rename `static_mut_ref` lint to `static_mut_refs`.
(cherry picked from commit 408eeae59d35cbcaab2cfb345d24373954e74fc5)
|
|
[beta-1.77.0] backport cargo
1 commits in 837c09f04022352c26cf445f37492709922b24ef..3fe68eabf93cbf3772bbcad09a9206c783e2de3f
2024-02-16 20:47:59 +0000 to 2024-02-29 00:16:03 +0000
- [beta-1.77] Backport ignore `cargo::rustc-check-cfg` (rust-lang/cargo#13500)
|
|
|
|
[beta-1.77.0] backport cargo
1 commits in c8a48facdaabe1d1fa8de11f90737801f38d8fa1..837c09f04022352c26cf445f37492709922b24ef
2024-02-07 19:15:46 +0000 to 2024-02-16 20:47:59 +0000
- [beta-1.77] chore: update jobserver to 0.1.28 (rust-lang/cargo#13452)
r? ghost
|
|
|
|
[beta] backports
- Correct paths for hexagon-unknown-none-elf platform doc #120533
- CI: Use ninja on apple builders #120543
- Correctly check `never_type` feature gating #120552
- Revert unsound libcore changes of 119911 #120562
- Downgrade xcode #120914
- Update jobserver-rs to 0.1.28 #120846
- [beta] Update LLVM submodule #121132
r? cuviper
|
|
(cherry picked from commit 7e1897cea0718043a776dba53281f69a1e97230a)
|
|
(cherry picked from commit 83f3bc42714250633cacadcde8b15da28bf443f0)
|
|
Allowing the Xcode version to "float" based on whatever default GitHub
selects creates an unreliable environment. When GitHub changes the
default, we can have multiple jobs in the same run using different
versions as it rolls out across machines. It can also cause oscillation
between runs as different machines are used. It also causes
unpredictable timing when the updates happen.
This change helps ensure that the version that is used is pinned. The
downside is that it requires manually bumping the version, and the risk
that if we take too long, older Xcodes will be removed and that will
break the build.
(cherry picked from commit 4ce1f1cffc7c63928cac447afe8010e6daaa42d6)
|
|
This seems to fix two sporadic errors that have been appearing in CI.
One is an issue with cmake being unable to verify that cmake is able to
build a simple test program. The other is a `invalid r_symbolnum`
linking error when trying to build one of cranelift's tests.
This is intended as a temporary fix until we can figure out how to
resolve those issues.
(cherry picked from commit 4fd3cf96a1db7771ef4f332b9eb1ad17fa0fd091)
|
|
(cherry picked from commit 6ac035df442a27cf9e99ab4ec25bb6147a700902)
|
|
(cherry picked from commit 0f21e45e95ea879ec13a690390c9d0bd327bfe58)
|
|
(cherry picked from commit 2c0030ff2cb373a31d4dfa7f7cb3596739090ff3)
|
|
(cherry picked from commit 2aebe6c302088dcd75ae18f40b40f6860c505450)
|
|
Update the library paths to correctly refer to libdemo{1,2}_hexagon
and switch to the release build instead.
Update references to libstandalone to the specific G0/PIC archive instead.
(cherry picked from commit 647a4536572ed51e15989ab82504df99aa9cc3bc)
|
|
[Beta 1.77] Fix bootstrapping from 1.76
Due to the timing of the revert for stabilization of c_str_literal (https://github.com/rust-lang/rust/pull/119528 which reverted in 1.76) and trait_upcasting (https://github.com/rust-lang/rust/pull/120269 which reverted in 1.76), which happened after https://github.com/rust-lang/rust/pull/119211 (Bump stage0 to 1.76 beta), this resulted in some of the feature attributes not being restored which are needed to be able to bootstrap from 1.76. This restores those features.
This also includes a stage0 bump to the just released stable. This is necessary because stage0 was currently pointing at an old beta which did not contain the reverts.
Fixes #120810
|
|
|
|
[beta-1.77.0] backport cargo
2 commits in 7bb7b539558dc88bea44cee4168b6269bf8177b0..c8a48facdaabe1d1fa8de11f90737801f38d8fa1
2024-01-20 00:15:32 +0000 to 2024-02-07 19:15:46 +0000
- [Beta-1.77] Update libgit2 (rust-lang/cargo#13417)
- [beta-1.77.0] Fix panic on empty spans when parsing Cargo.toml (rust-lang/cargo#13393)
|
|
|
|
|
|
[beta] initial branch of 1.77
https://forge.rust-lang.org/release/process.html#promote-branches-t-3-days-monday
r? `@Mark-Simulacrum`
|
