summary refs log tree commit diff
AgeCommit message (Collapse)AuthorLines
2023-12-21Auto merge of #119188 - flip1995:clippy-beta-backport, r=pietroalbini 1.75.0bors-230/+368
[beta] Clippy beta backport PR towards stable, as beta was branched a day early and I missed the notification. - https://github.com/rust-lang/rust-clippy/pull/11538 - https://github.com/rust-lang/rust-clippy/pull/11756 - https://github.com/rust-lang/rust-clippy/pull/11760 - https://github.com/rust-lang/rust-clippy/pull/11953 r? `@pietroalbini`
2023-12-21Auto merge of #11953 - Jarcho:issue_11952, r=Alexendoobors-103/+150
Fix binder handling in `unnecessary_to_owned` fixes #11952 The use of `rebind` instead of `EarlyBinder::bind` isn't technically needed, but it is the semantically correct operation. changelog: None
2023-12-21Auto merge of #11760 - compiler-errors:escaping, r=Jarchobors-2/+18
Don't check for late-bound vars, check for escaping bound vars Fixes an assertion that didn't make sense. Many valid and well-formed types *have* late-bound vars (e.g. `for<'a> fn(&'a ())`), they just must not have *escaping* late-bound vars in order to be normalized correctly. Addresses rust-lang/rust-clippy#11230, cc `@jyn514` and `@matthiaskrgr` changelog: don't check for late-bound vars, check for escaping bound vars. Addresses rust-lang/rust-clippy#11230
2023-12-21Auto merge of #11756 - y21:issue11755, r=Manishearthbors-3/+8
[`unused_enumerate_index`]: don't ICE on empty tuples Fixes #11755 changelog: [`unused_enumerate_index`]: don't ICE on empty tuples I'm going to nominate for beta backport because the code that is needed to trigger this seems likely to occur in real code `@rustbot` label +beta-nominated
2023-12-21Auto merge of #11538 - Jarcho:proc_mac, r=dswijbors-122/+192
Fix `is_from_proc_macro` patterns fixes #11533 changelog: none
2023-12-21Auto merge of #119186 - rust-lang:pa-stable-1.75, r=pietroalbinibors-2/+249
[stable] Prepare Rust 1.75.0 release This PR includes the squash of the release notes from https://github.com/rust-lang/rust/pull/118729, and bumps the channel to stable to prepare release artifacts. The only `beta-nominated` PR is https://github.com/rust-lang/rust/pull/118796, which is still waiting for review and is not `beta-accepted` yet, so this does **not** backport it. `@Nadrieril` `@cjgillot` `@apiraino` if that PR becomes ready to be backported before the 28th ping me on Zulip and I can rebuild artifacts with it. r? `@ghost`
2023-12-21bump channel to stablePietro Albini-1/+1
2023-12-21update release notesPietro Albini-1/+248
2023-12-16Auto merge of #118994 - cuviper:beta-next, r=cuviperbors-13/+29
[beta] backports - temporarily revert "ice on ambguity in mir typeck" #118736 - Update to LLVM 17.0.6 #118936 r? ghost
2023-12-15Include an additional cherry-pickNikita Popov-0/+0
(cherry picked from commit 601d52a7031f0f57562b661c99d30b4035d7b4af)
2023-12-15Update to LLVM 17.0.6Nikita Popov-1/+1
(cherry picked from commit bb7c483e48ea992f3759fb643962e1e706c8c029)
2023-12-15temporarily revert "ice on ambguity in mir typeck"Ali MJ Al-Nasrawy-12/+28
Reverts #116530 (cherry picked from commit 5fdb648fc3a672140f3fc8f98ee3268ed3fe5389)
2023-12-13Auto merge of #118837 - cuviper:beta-next, r=cuviperbors-1/+1
[beta] Update backtrace submodule * Update backtrace submodule #118137 As well as infrastructure fix: * Don't ask for a specific branch in cargotest #118597 r? ghost
2023-12-12Don't ask for a specific branch in cargotestLaurențiu Nicola-1/+1
(cherry picked from commit 5808b72484204af035a4d9683731f44bd8d59529)
2023-12-11Update backtrace submoduleroblabla-0/+0
(cherry picked from commit 08803eb4c87b3b1895fae1d071229c1cf23b39d5)
2023-12-01Auto merge of #118492 - cuviper:beta-next, r=cuviperbors-29/+145
[beta] backports - Build pre-coroutine-transform coroutine body #117686 - Fix coroutine validation for mixed panic strategy #118422 - ConstProp: Remove const when rvalue check fails. #118426 - Dispose llvm::TargetMachines prior to llvm::Context being disposed #118464 r? ghost
2023-11-30Update compiler/rustc_codegen_llvm/src/lib.rsWesley Wiser-1/+1
Co-authored-by: Josh Stone <cuviper@gmail.com> (cherry picked from commit 10110787154154cddfaaacdeebd7a4406223a25b)
2023-11-30Dispose llvm::TargetMachines prior to llvm::Context being disposedWesley Wiser-6/+18
If the TargetMachine is disposed after the Context is disposed, it can lead to use after frees in some cases. I've observed this happening occasionally on code compiled for aarch64-pc-windows-msvc using `-Zstack-protector=strong` but other users have reported AVs from host aarch64-pc-windows-msvc compilers as well. (cherry picked from commit 3323e4dc04e57cc64ac77dbff2f6bf50ac6832f0)
2023-11-30Rename and add another testAlona Enraght-Moony-3/+30
(cherry picked from commit 6e956c0a383444a25cc0e690cbc9fa6f859b07b4)
2023-11-30ConstProp: Remove const when rvalue check fails.Alona Enraght-Moony-3/+7
(cherry picked from commit 9121a41450e905fe5a12c11c955acc14ab1f92fe)
2023-11-30Precommit test for https://github.com/rust-lang/rust/issues/118328.Alona Enraght-Moony-0/+41
(cherry picked from commit b1a6cf4a0e7d6727516e943d86fdab8587b94722)
2023-11-30Fix coroutine validation for mixed panic strategyTomasz Miąsko-11/+28
Validation introduced in #113124 allows UnwindAction::Continue and TerminatorKind::Resume to occur only in functions with ABI that can unwind. The function ABI depends on the panic strategy, which can vary across crates. Usually MIR is built and validated in the same crate. The coroutine drop glue thus far was an exception. As a result validation could fail when mixing different panic strategies. Avoid the problem by executing AbortUnwindingCalls along with the validation. (cherry picked from commit 5161b22143bf9a726cfd69d19bef11552d0ed519)
2023-11-30Build pre-coroutine-transform coroutine bodyMichael Goulet-11/+26
(cherry picked from commit 0ba7d19769c068729761eba72e779b53101a19bc)
2023-11-28Auto merge of #118390 - cuviper:beta-next, r=cuviperbors-4/+10
[beta] backports - feat: implement `DoubleEndedSearcher` for `CharArray[Ref]Searcher` #111922 - Update to LLVM 17.0.5 #117907 - clarify `fn discriminant` guarantees: only free lifetimes may get erased #118006 r? ghost
2023-11-27only free lifetimes may get erasedlcnr-4/+6
(cherry picked from commit 3b0e1d23b7fff6b57a634f529ee19d0d173a95f7)
2023-11-27Update to LLVM 17.0.5Nikita Popov-0/+0
(cherry picked from commit 8e2fcc4ca211021d929ca424055b59307a97a8f4)
2023-11-27feat: implement `DoubleEndedSearcher` for `CharArray[Ref]Searcher`Jan-0/+4
(cherry picked from commit c6ed532bef02e752ea881ab104cacc28e5d06738)
2023-11-20Auto merge of #118093 - weihanglo:update-beta-cargo, r=weihanglobors-0/+0
[beta-1.75] Update cargo 2 commits in 6790a5127895debec95c24aefaeb18e059270df3..1d8b05cdd1287c64467306cf3ca2c8ac60c11eb0 2023-11-10 17:09:35 +0000 to 2023-11-20 01:39:31 +0000 - [beta-1.75.0] chore: bump `cargo-credential-*` crates as e58b84d broke stuff (rust-lang/cargo#13009) - [beta 1.75] Backport 1password fixes (rust-lang/cargo#12994) r? ghost
2023-11-20[beta-1.75] Update cargoWeihang Lo-0/+0
2023-11-18Auto merge of #118042 - Mark-Simulacrum:beta-next, r=Mark-Simulacrumbors-378/+375
[beta] backport & bootstrap bump Bumps the bootstrap compiler to released 1.74, and lands the first backport: - #117827: coverage: Avoid creating malformed macro name spans r? `@Mark-Simulacrum`
2023-11-18coverage: Regression test for #117788Zalathar-0/+90
Without the workaround applied, this test will produce malformed mappings that cause `llvm-cov` to fail. (And if it does emit well-formed mappings, they should be obviously incorrect.)
2023-11-18coverage: Avoid creating malformed macro name spansZalathar-0/+6
This method is trying to detect macro invocations, so that it can split a span into two parts just after the `!` of the invocation. Under some circumstances (probably involving nested macros), it gets confused and produces a span that is larger than the original span, and possibly extends outside its enclosing function and even into an adjacent file. In extreme cases, that can result in malformed coverage mappings that cause `llvm-cov` to fail. For now, we at least want to detect these egregious cases and avoid them, so that coverage reports can still be produced.
2023-11-18Bump bootstrap to released 1.74.0Mark Rousskov-378/+279
2023-11-12Auto merge of #117842 - Mark-Simulacrum:beta-next, r=Mark-Simulacrumbors-85/+82
[beta] 1.75.0 promotion https://forge.rust-lang.org/release/process.html#promote-branches-t-3-days-monday r? `@Mark-Simulacrum`
2023-11-12Cranelift isn't available on non-nightly channelsMark Rousskov-4/+1
2023-11-12Bump channel to betaMark Rousskov-1/+1
2023-11-12Substitute version placeholdersMark Rousskov-80/+80
2023-11-11Auto merge of #117797 - weihanglo:update-cargo, r=weihanglobors-0/+1
Update cargo 12 commits in 7046d992f9f32ba209a8079f662ebccf9da8de25..6790a5127895debec95c24aefaeb18e059270df3 2023-11-08 03:24:57 +0000 to 2023-11-10 17:09:35 +0000 - refactor(source): Prepare for new PackageIDSpec syntax (rust-lang/cargo#12938) - credential: include license files in all published crates (rust-lang/cargo#12953) - fix: preserve jobserver file descriptors on rustc invocation in `fix_exec_rustc` (rust-lang/cargo#12951) - refactor(resolver): Consolidate logic in `VersionPreferences` (rust-lang/cargo#12930) - refactor(toml): Simplify code to make schema split easier (rust-lang/cargo#12948) - Filter `cargo-credential-*` dependencies by OS (rust-lang/cargo#12949) - refactor(util): Pull out `mod util_semver` (rust-lang/cargo#12940) - Fix the invalidate feature name message (rust-lang/cargo#12939) - refactor(util): Prepare for splitting out semver logic (rust-lang/cargo#12926) - feat: Make browser links out of HTML file paths (rust-lang/cargo#12889) - Do not allow empty feature name (rust-lang/cargo#12928) - fix(timings): unnecessary backslash when error happens (rust-lang/cargo#12934) r? ghost
2023-11-11Auto merge of #117799 - erickt:fuchsia, r=tmandrybors-8/+44
Switch `fuchsia-test-runner.py` to `ffx product` The subcommand `ffx product-bundle` has been removed, and replaced with the subcommand `ffx product`. This changes `fuchsia-test-runner.py` to use it to download the SDK and product bundle for the latest release of Fuchsia.
2023-11-10Switch `fuchsia-test-runner.py` to `ffx product`Erick Tryzelaar-8/+44
The subcommand `ffx product-bundle` has been removed, and replaced with the subcommand `ffx product`. This changes `fuchsia-test-runner.py` to use it to download the SDK and product bundle for the latest release of Fuchsia.
2023-11-10Update cargoWeihang Lo-0/+1
2023-11-10Auto merge of #115229 - iSwapna:issue-115222-fix, r=estebankbors-3/+84
On method chain expression failure, look for missing method in earlier segments of the chain This PR tries to fix the issue: https://github.com/rust-lang/rust/issues/115222 As suggested by `@estebank` , I did the following: 1. Add new test `tests/ui/structs/method-chain-expression-failure.rs` 2. In `compiler/rusct_hir_tycheck/src/method/suggest.rs` walking up the method chain and calling `probe_for_name` with the method name. But the call fails to return `Ok`.
2023-11-10Recurse over the method chain and maintain a stack to peek at previous ↵Swapna Iyer-3/+84
receiver to align spans
2023-11-10Auto merge of #117779 - bjorn3:sync_cg_clif-2023-11-10, r=bjorn3bors-67/+961
Subtree update for rustc_codegen_cranelift Significantly improved support for simd intrinsics. r? `@ghost` `@rustbot` label +A-codegen +A-cranelift +T-compiler
2023-11-10Merge commit 'c84d1871dc4456539b7b578830268ab3539915d0' into ↵bjorn3-67/+961
sync_cg_clif-2023-11-10
2023-11-10Rustup to rustc 1.75.0-nightly (0f44eb32f 2023-11-09)bjorn3-6/+5
2023-11-10Sync from rust 0f44eb32f1123ac93ab404d74c295263ce468343bjorn3-1/+0
2023-11-10Auto merge of #117765 - onur-ozkan:fix-117762, r=clubby789bors-0/+6
enable unstable feature on `x clean [PATH]` Since https://github.com/rust-lang/rust/pull/111076 enables unstable cargo feature (`public-dependency`), we need to ensure that unstable features are enabled before reading libstd Cargo.toml. Fixes #117762 cc `@Nilstrieb`
2023-11-10Auto merge of #117572 - RalfJung:addr_of, r=cuviperbors-6/+24
update and clarify addr_of docs This updates the docs to match https://github.com/rust-lang/reference/pull/1387. Cc `@rust-lang/opsem` `@chorman0773` not sure if you had anything else you wanted to say here, I'd be happy to get your feedback. :) Fixes https://github.com/rust-lang/rust/issues/114902, so Cc `@joshlf`
2023-11-10mention null explicitlyRalf Jung-2/+2
Co-authored-by: Josh Stone <cuviper@gmail.com>