| Age | Commit message (Collapse) | Author | Lines |
|
|
|
|
|
|
|
ADTs are translated in-place from rustc_trans::callee, so no trans-items
are needed.
This fix will be superseded by the shimmir branch, but I prefer not to
backport that to beta.
Fixes #39823.
|
|
|
|
Fix #40221 and add unittest.
|
|
|
|
PRs can't land againt beta right now because the android bot is filling up on
disk space. I don't really know what's going on but the android bot is the
longest one to run anyway so it'll benefit from being split up regardless.
|
|
Add the `?Sized` bound as we don't require the type to be sized.
Closes #40011
|
|
This is a [breaking-change] from 1.15, because this used to compile:
```Rust
enum Void {}
fn foo(x: &Void) {
match x {}
}
```
|
|
Fixes #38972.
|
|
|
|
|
|
|
|
|
|
|
|
The function was a footgun because it created `undef` references to
ZSTs, which could cause trouble were they to leak to user code.
|
|
|
|
According to the LLVM reference:
> A value of 0 or an omitted align argument means that the operation has
the ABI alignment for the target.
So loads/stores of fields of packed structs need to have their align set
to 1. Implement that by tracking the alignment of `LvalueRef`s.
Fixes #39376.
|
|
|
|
|
|
|
|
|
|
|
|
These are some samples that I have been focusing on improving over
time. In this PR, I mainly want to stem the bleeding where we in some
cases we show an error that gives you no possible way to divine the
problem.
|
|
The previous fix contained an error where `toml::encode` returned a runtime
error, so this version just constructs a literal `toml::Value`.
|
|
Right now we just run `shasum` on an absolute path but right now the shasum
files only include filenames, so let's use `current_dir` and just the file name
to only have the file name emitted.
|
|
The current manifests encode this with a dash in the name, so we should preserve
that!
|
|
Prevents stale artifacts from sticking around by accident!
|
|
[beta] Backporting PRs to beta
This is a backport of the following PRs:
* https://github.com/rust-lang/rust/pull/39478
* https://github.com/rust-lang/rust/pull/39509
* https://github.com/rust-lang/rust/pull/39517
* https://github.com/rust-lang/rust/pull/39526
* https://github.com/rust-lang/rust/pull/39599
* https://github.com/rust-lang/rust/pull/39624
* https://github.com/rust-lang/rust/pull/39710
|
|
[beta] Update bootstrap compiler to 1.15.1
|
|
[beta] Fix a manifest-generation bug on beta
This is a beta backport of https://github.com/rust-lang/rust/pull/39599
|
|
Right now all Cargo release tarballs are 'nightly', they're not on the standard
channels yet.
|
|
|
|
|
|
|
|
|
|
We should be sure to add our build system entry point!
Closes #39476
|
|
|
|
[beta] rustbuild: Pass -fPIC on 32-bit non-Windows platforms
This is a smaller and more targeted backport of #39523 which drives to the heart
of the issue, just passing `-fPIC` on 32-bit platforms. More rationale for this
commit can be found in #39523 itself.
|
|
This is a smaller and more targeted backport of #39523 which drives to the heart
of the issue, just passing `-fPIC` on 32-bit platforms. More rationale for this
commit can be found in #39523 itself.
|
|
Right now all Cargo release tarballs are 'nightly', they're not on the standard
channels yet.
|
|
[beta] std: Fix IntoIter::as_mut_slice's signature
This is a backport of #39466 to beta
|
|
[beta] Give a better error message for unknown derive messages
This PR improves the error message for unknown derive macros.
Currently unknown derives give the following error, which is very misleading:
```
`#[derive]` for custom traits is not stable enough for use. It is deprecated and will be removed in v1.15 (see issue #29644)
```
I'm currently working on a PR that will change this (https://github.com/rust-lang/rust/pull/39442) to the following:
```
cannot find derive macro `Foo` in this scope
```
This PR backports the (as yet unmerged) error message to beta/1.16 (it's a pity that this is probably too late for 1.15).
r? @jseyfried
|
|
This was a mistake not exercised until just now!
|
|
|
|
This was intended to require `&mut self`, not `&self`, otherwise it's unsound!
Closes #39465
|
|
|
|
|
|
|