| Age | Commit message (Collapse) | Author | Lines |
|
[stable] 1.43.1 release
* [Updated openssl-src to 1.1.1g for CVE-2020-1967.][71430]
* [Fixed the stabilization of AVX-512 features.][71473]
* [Fixed `cargo package --list` not working with unpublished dependencies.][cargo/8151]
[71430]: https://github.com/rust-lang/rust/pull/71430
[71473]: https://github.com/rust-lang/rust/issues/71473
[cargo/8151]: https://github.com/rust-lang/cargo/issues/8151
|
|
|
|
The upstream archive went down due to an expired certificate, so I
mirrored the whole thing on our mirrors S3 bucket. This is safe, as the
certificate just seemed to be expired and the contents of the APT
archive are signed anyway.
|
|
|
|
|
|
|
|
|
|
Fixes CVE-2020-1967.
|
|
[stable] 1.43.0 release
Includes a last minute backport of https://github.com/rust-lang/rust/pull/71267.
|
|
|
|
(My hypothesis is that my use of this flag was an overly conservative
generalization of PR 67020.)
|
|
|
|
[beta] backports
This includes:
* Do not reuse post LTO products when exports change #71131
* macro_rules: `NtLifetime` cannot start with an identifier #70768
* Update RELEASES.md for 1.43.0 #70354
r? @ghost
|
|
|
|
|
|
|
|
Renamed the struct to make it a little clearer that it doesn't just hold one
imports map. (I couldn't bring myself to write it as `ThinLTOImportsExports`
though, mainly since the exports map is literally derived from the imports map
data.) Added some doc to the struct too.
Revised comments to add link to the newer issue that discusses why the exports
are relevant.
Renamed a few of the methods so that the two character difference is more
apparent (because 1. the method name is shorter and, perhaps more importantly,
the changed characters now lie at the beginning of the method name.)
|
|
Namely, a regression test for issue #69798 (export added), and the inverse of
that test (export removd).
|
|
incremental compilation.
This is symmetric to PR #67020, which handled the case where the LLVM module's
*imports* changed. This commit builds upon the infrastructure added there; the
export map is just the inverse of the import map, so we can build the export map
at the same time that we load the serialized import map.
Fix #69798
|
|
[beta] backports
* Use TypeRelating for instantiating query responses #69591
* Move rustc-guide submodule to rustc-dev-guide #69898
|
|
Co-Authored-By: Mateusz Mikuła <mati865@users.noreply.github.com>
|
|
|
|
|
|
[beta] backport 4 PRs
This backports the following PRs:
* parse_and_disallow_postfix_after_cast: account for `ExprKind::Err`. #70556
* Account for bad placeholder types in where clauses #70294
* Fix "since" field for `Once::is_complete`'s `#[stable]` attribute #70018
* Ensure HAS_FREE_LOCAL_NAMES is set for ReFree #69956
All commits cherry picked cleanly.
|
|
|
|
It was accidentally merged with the wrong version.
|
|
|
|
|
|
[beta] 1.43: don't pass -Zconfig-profile to cargo when self rebuilding
This option is now stable thus our cargo will reject it
Fixes #69975
|
|
This option is now stable thus our cargo will reject it
Fixes #69975
Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
|
|
[beta] backport rollup
This backports:
* can_begin_literal_maybe_minus: `true` on `"-"? lit` NTs. #70058
* ci: use python from the correct path #70116
* Update stdarch submodule #70151 (superseding and closing #70221)
* Beta: Update cargo, clippy #70105 (also closing that beta-targeted PR)
It also switches the bootstrap compiler to download from static.rust-lang.org from dev-static.rust-lang.org.
|
|
|
|
|
|
|
|
Apparently the old path we were using for Python 2 on Windows was not
documented, and eventually got removed. This switches our CI to use the
correct path.
|
|
|
|
[beta] Promote 1.43.0 to beta
This time pointing to the right branch.
|
|
|
|
|
|
Rollup of 10 pull requests
Successful merges:
- #69475 (Remove the `no_force` query attribute)
- #69514 (Remove spotlight)
- #69677 (rustc_metadata: Give decoder access to whole crate store)
- #69714 (Make PlaceRef take just one lifetime)
- #69799 (Allow ZSTs in `AllocRef`)
- #69817 (test(patterns): add patterns feature tests to borrowck test suite)
- #69836 (Check if output is immediate value)
- #69847 (clean up E0393 explanation)
- #69861 (Add note about localization to std::fmt docs)
- #69877 (Vec::new is const stable in 1.39 not 1.32)
Failed merges:
r? @ghost
|
|
Vec::new is const stable in 1.39 not 1.32
Changelog: https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-1390-2019-11-07
This really surprised me when a MSRV check for 1.35 failed with `Vec::new is not yet stable as a const fn` and the docs said that it was const stabilized in 1.32.
|
|
Add note about localization to std::fmt docs
Closes #69681
|
|
clean up E0393 explanation
r? @Dylan-DPC
|
|
Check if output is immediate value
Fixes #62046
r? @nagisa
|
|
r=Centril
test(patterns): add patterns feature tests to borrowck test suite
Addresses request here: https://github.com/rust-lang/rust/pull/69690#issuecomment-595763571
Fixes https://github.com/rust-lang/rust/issues/67311.
r? @Centril
|
|
Allow ZSTs in `AllocRef`
Allows ZSTs in all `AllocRef` methods. The implementation of `AllocRef` for `Global` and `System` were adjusted to reflect those changes.
This is the second item on the roadmap to support ZSTs in `AllocRef`: https://github.com/rust-lang/wg-allocators/issues/38#issuecomment-595861542
After this has landed, I will adapt `RawVec`, but since this will be a pretty big overhaul, it makes sense to do a different PR for it.
~~Requires #69794 to land first~~
r? @Amanieu
|
|
Make PlaceRef take just one lifetime
r? @eddyb
|
|
rustc_metadata: Give decoder access to whole crate store
Pre-requisite for https://github.com/rust-lang/rust/pull/68941.
r? @eddyb
|
|
Remove spotlight
I had a few comments saying that this feature was at best misunderstood or not even used so I decided to organize a poll about on [twitter](https://twitter.com/imperioworld_/status/1232769353503956994). After 87 votes, the result is very clear: it's not useful. Considering the amount of code we have just to run it, I think it's definitely worth it to remove it.
r? @kinnison
cc @ollie27
|
|
Remove the `no_force` query attribute
This removes the `no_force` query attribute and instead uses the `DepNodeParams` trait to find out if a query can be forced.
Also the `analysis` query is moved to the query macro.
r? @eddyb
|