| Age | Commit message (Collapse) | Author | Lines |
|
|
|
[beta] Disable lints in rustdoc
The lint handling in rustdoc 1.28 is still incomplete so I think it would be best to disable it for the stable release. The main thing that's missing is that cargo doesn't cap lints for dependencies. This was fixed in master by #52354 and rust-lang/cargo#5765 but they haven't been backported. Additionally rustdoc is still emitting lints that are not on its whitelist https://github.com/rust-lang/rust/issues/51661#issuecomment-406800119.
cc. @rust-lang/rustdoc
|
|
|
|
|
|
failure.
Rather than try to work out what was happening, I just removed the flag because
I see no reason for it to be on this test.
|
|
|
|
Therefore we cannot coerce it to a supertype the same way that we can
the LHS of `+`.
Addresses issue 52126.
|
|
beta: only true stage0 needs feature(global_allocator)
We use `#[global_allocator]` for `stage0` builds of libstd, and also
with `feature = "force_alloc_system"` that's set for a local rebuild,
where the bootstrap compiler is the same version and otherwise uses the
`--cfg stage1`.
We only need the unstable `feature(global_allocator)` for a true `stage0`
being 1.27. For rebuilds with 1.28, that feature is stable and causes a
denied warning if it's enabled, so we should avoid it.
|
|
We use `#[global_allocator]` for `stage0` builds of libstd, and also
with `feature = "force_alloc_system"` that's set for a local rebuild,
where the bootstrap compiler is the same version and otherwise uses the
`--cfg stage1`.
We only need the unstable `feature(global_allocator)` for a true `stage0`
being 1.27. For rebuilds with 1.28, that feature is stable and causes a
denied warning if it's enabled, so we should avoid it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[beta] Abort instead of UB if promotion fails
original PR: https://github.com/rust-lang/rust/pull/52571 (not beta approved yet)
r? @nikomatsakis
cc @RalfJung
|
|
|
|
- [beta] Partially revert dep changes in rust-lang/cargo#5651 (rust-lang/cargo#5722)
|
|
Fixes: #52029
|
|
|
|
I don't see why MC should fail on well-formed code, so it might be a
better idea to just add a `delay_span_bug` there (anyone remember the
`cat_expr Errd` bug from the 1.0 days?).
However, I don't think this is a good idea to backport a new delay_span_bug
into stable and this code is going away soon-ish anyway.
|
|
This looks like a typo introduced in #51686.
Fixes #52213.
|
|
|
|
|
|
|
|
|
|
See CVE-2018-1000622.
|
|
this gives us some leeway when optimizing
|
|
- [BETA] Fix doctests linking too many libs. (rust-lang/cargo#5687)
- [beta] Fix `cargo install` using a workspace target dir (rust-lang/cargo#5686)
|
|
This commit updates the `stdsimd` module on the beta branch to pull in a fix for
rust-lang-nursery/stdsimd#500, a bug which affects the stable 1.27.0 release
which causes feature detection on x86 to cause an illegal instruction on some
CPUs.
|
|
|
|
|
|
|
|
|
|
Update beta Cargo
This pulls in https://github.com/rust-lang/cargo/pull/5671.
It should permit us to bootstrap from the new beta compiler
successfully.
r? @alexcrichton
|
|
This pulls in https://github.com/rust-lang/cargo/pull/5671.
It should permit us to bootstrap from the new beta compiler
successfully.
|
|
https://github.com/rust-lang/llvm/pull/118
https://github.com/rust-lang/llvm/pull/119
|
|
|
|
|
|
|
|
|
|
- we need to figure out hygiene first
- change the test to check that the prohibition works with a good error
msg
- leaves some comments and debugging code
- leaves some of our supposed fixes
|
|
|
|
|
|
|
|
|
|
None of the tools in the list should need LLVM tools themselves as far as I can
tell; if this is incorrect, we can re-enable the tool building later.
The primary reason for doing this is that rust-central-station uses the
BuildManifest tool and building LLVM there is not cached: it takes ~1.5
hours on the 2 core machine. This commit should make nightlies and
stable releases much faster.
|