| Age | Commit message (Collapse) | Author | Lines |
|
[stable] Prepare 1.76.0 release
https://forge.rust-lang.org/release/process.html#promote-branches-t-3-days-monday
No last minute backports this time (at least yet).
r? `@Mark-Simulacrum`
|
|
|
|
[beta] backports
- Remove alignment-changing in-place collect #120116
- fix: Drop guard was deallocating with the incorrect size #120145
r? ghost
|
|
InPlaceDstBufDrop holds onto the allocation before the shrinking happens
which means it must deallocate the destination elements but the source
allocation.
(cherry picked from commit 5796b3c16733f3d9cb2f3476ed1dc0fe05b14e25)
|
|
Currently stable users can't benefit from this because GlobaAlloc doesn't support
alignment-changing realloc and neither do most posix allocators.
So in practice it always results in an extra memcpy.
(cherry picked from commit 85d17879623116be76a68c2170c4cb6ff58f4ceb)
|
|
(cherry picked from commit b28a95391b85e17b1d2f7edc1115291d8a86bcd2)
|
|
r=jackh726
[beta] Revert trait obj upcast stabilization
backport of https://github.com/rust-lang/rust/pull/120233
note that this is not yet approved for beta backport
|
|
|
|
This reverts commit 6d2b84b3ed7848fd91b8d6151d4451b3103ed816, reversing
changes made to 73bc12199ea8c7651ed98b069c0dd6b0bb5fabcf.
|
|
[beta-1.76.0] backport cargo
1 commits in ddec30889aff0c38118bcbeb59597d0bd85eddcd..c84b367471a2db61d2c2c6aab605b14130b8a31b
2024-01-02 23:23:28 +0000 to 2024-01-18 16:17:02 +0000
- [beta-1.76.0] fix(`--package`): accept `?` if it's a valid pkgid spec (rust-lang/cargo#13318)
r? ghost
|
|
[beta] Revert #113923
Per [#t-compiler/meetings > [weekly] 2024-01-11](https://rust-lang.zulipchat.com/#narrow/stream/238009-t-compiler.2Fmeetings/topic/.5Bweekly.5D.202024-01-11) discussion, revert #113923. Also revert associated #118568.
The PR #113923 causes the regression issue #118609. We need more time to find a proper solution.
Discussions start at [412365838](https://rust-lang.zulipchat.com/#narrow/stream/238009-t-compiler.2Fmeetings/topic/.5Bweekly.5D.202024-01-11/near/412365838) and continue to [412369643](https://rust-lang.zulipchat.com/#narrow/stream/238009-t-compiler.2Fmeetings/topic/.5Bweekly.5D.202024-01-11/near/412369643).
Fixes #118609.
Same as #119885 but backported to beta.
r? compiler
|
|
|
|
This reverts commit 8c2b57721728233e074db69d93517614de338055, reversing
changes made to 9cf18e98f82d85fa41141391d54485b8747da46f.
|
|
This reverts commit 503e129328080e924c0ddfca6abf4c2812580102, reversing
changes made to 0e7f91b75e7484a713e2f644212cfc1aa7478a28.
|
|
[beta] backports
- mir-opt and custom target fixes #119619
- Update LLVM submodule #119802
r? ghost
|
|
(cherry picked from commit 9ff3083b27e396740689a722ca493c0878bdcd6c)
|
|
Signed-off-by: onur-ozkan <work@onurozkan.dev>
(cherry picked from commit b888e2f82b9dbe81875f50d13adbc0271a9401ff)
|
|
Signed-off-by: onur-ozkan <work@onurozkan.dev>
(cherry picked from commit 26c71cbcf1a9bce6ceb962d753c467d098f63cf6)
|
|
Signed-off-by: onur-ozkan <work@onurozkan.dev>
(cherry picked from commit 8aa7dd06f6e50621dc10f9f9490681be8a45876f)
|
|
[beta] rustdoc ui: adjust tooltip z-index to be above sidebar
Backport of https://github.com/rust-lang/rust/pull/119477.
Fixes https://github.com/rust-lang/rust/issues/119472.
range-diff:
```range-diff
446: d796ad4209b = 11: 53637cdd8ed rustdoc ui: adjust tooltip z-index to be above sidebar
459: b1853eb3bd5 ! 12: c4c4ff67fae use css variable for z-index of the sidebar
`@@` src/librustdoc/html/static/css/rustdoc.css: so that we can apply CSS-filters to
margin-top: 7px;
border-radius: 3px;
border: 1px solid var(--border-color);
-`@@` src/librustdoc/html/static/css/rustdoc.css: a.tooltip:hover::after {
- }
- .src #sidebar-button {
- left: 8px;
-- z-index: 101;
-+ z-index: calc(var(--desktop-sidebar-z-index) + 1);
- }
- .hide-sidebar .src #sidebar-button {
- position: static;
```
The "show sidebar" button on the [source view page](https://doc.rust-lang.org/nightly/src/std/lib.rs.html) works differently on beta and nightly, but it is in fact above the sidebar in both versions.
beta button:

nightly button:

cc `@Mark-Simulacrum`
|
|
[beta] Revert #117472: Stabilize C string literals
Based on discussion in [#t-lang](https://rust-lang.zulipchat.com/#narrow/stream/213817-t-lang/topic/rfc.203349.3A.20mixed.20utf8.20literals), revert the stabilization of C string literals in Rust 1.76.
I also reverted #118566 as it uses the newly stabilized C string literals in various places.
|
|
|
|
and calculate the z-indices of things that go over the sidebar
|
|
|
|
[beta] backport rollup
This PR backports:
- #119544: Fix: Properly set vendor in i686-win7-windows-msvc target
- #118796: Exhaustiveness: Improve complexity on some wide matches
- #119546: Temporarily disable M1 runners on GitHub Actions
- #119584: [beta] Clippy (early) beta backport
- #119559: [beta-1.76] Update cargo
And also:
- Bumps stage0 to released stable.
r? `@Mark-Simulacrum`
|
|
|
|
|
|
This commit temporarily reverts the addition of M1 runners on GitHub
Actions to work around a billing issue related to their beta. It also
removes the `aarch64-apple` job, which was only added after the addition
of M1 runners. Since it has never been tested on the prior hardware, we
are skipping the tests to reduce the risk of build failures.
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit 0f41bc21b958fed66b3d055531af67638390f520.
|
|
[beta] Prepare 1.76 beta
This PR bumps the channel to beta and updates the version placeholders for stabilizations.
r? `@ghost`
|
|
|
|
|
|
|
|
Tolerate overaligned MIR constants for codegen.
Fixes https://github.com/rust-lang/rust/issues/117761
cc `@saethlin`
|
|
Rollup of 5 pull requests
Successful merges:
- #119135 (Fix crash due to `CrateItem::kind()` not handling constructors)
- #119141 (Add method to get instance instantiation arguments)
- #119145 (Give `VariantData::Struct` named fields, to clairfy `recovered`.)
- #119167 (E0761: module directory has .rs suffix)
- #119168 (resolve: Stop feeding visibilities for import list stems)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
resolve: Stop feeding visibilities for import list stems
Fixes https://github.com/rust-lang/rust/issues/119126
|
|
E0761: module directory has .rs suffix
`rustc --explain E0761` example seems wrong.
|
|
r=compiler-errors
Give `VariantData::Struct` named fields, to clairfy `recovered`.
Implements https://github.com/rust-lang/rust/pull/119121#discussion_r1431467066. Supersedes #119121
This way, it's clear what the bool fields means, instead of having to find where it's generated. Changes both ast and hir.
r? `@compiler-errors`
|
|
Add method to get instance instantiation arguments
Add a method to get the instance instantiation arguments, and include that information in the instance debug.
|
|
Fix crash due to `CrateItem::kind()` not handling constructors
Also add a method to get the instance instantiation arguments, and include that information in the instance debug.
|
|
|
|
|
|
|
|
Change how we classify item kind for DefKind::Ctor
|
|
do not allow ABI mismatches inside repr(C) types
In https://github.com/rust-lang/rust/pull/115476 we allowed ABI mismatches inside `repr(C)` types. This wasn't really discussed much; I added it because from how I understand calling conventions, this should actually be safe in practice. However I entirely forgot to actually allow this in Miri, and in the mean time I have learned that too much ABI compatibility can be a problem for CFI (it can reject fewer calls so that gives an attacker more room to play with).
So I propose we take back that part about ABI compatibility in `repr(C)`. It is anyway something that C and C++ do not allow, as far as I understand.
In the future we might want to introduce a class of ABI compatibilities where we say "this is a bug and it may lead to aborting the process, but it won't lead to arbitrary misbehavior -- worst case it'll just transmute the arguments from the caller type to the callee type". That would give CFI leeway to reject such calls without introducing the risk of arbitrary UB. (The UB can still happen if the transmute leads to bad results, of course, but it wouldn't be due to ABI weirdness.)
#115476 hasn't reached beta yet so if we land this before Dec 22nd we can just pretend this all never happened. ;) Otherwise we should do a beta backport (of the docs change at least).
Cc `@rust-lang/opsem` `@rust-lang/types`
|