rust/src/test/incremental, branch 1.46.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.46.02020-05-25T06:17:15+00:00Auto merge of #72520 - jonas-schievink:cleanup-userty, r=matthewjasper2020-05-25T06:17:15+00:00borsbors@rust-lang.org2020-05-25T06:17:15+00:00urn:sha1:997d953eeec0be62c59ea028c95cd7be49adf58f
Clear MIR local type annotations after borrowck
Clear MIR local type annotations after borrowck2020-05-24T02:15:23+00:00Jonas Schievinkjonasschievink@gmail.com2020-05-24T00:57:21+00:00urn:sha1:235929953719661e70e152e63521a1c446d76cafAdd missing ASM arena declaration to librustc_middle2020-05-23T19:50:37+00:00Aaron Hillaa1ronham@gmail.com2020-05-20T21:39:19+00:00urn:sha1:8da494272f4c162c4a853e325a6bd33a80881ff6
Fixes #72386
This type also needs to get allocated on the `librustc_middle` arena
when we deserialize MIR.
Rollup merge of #72045 - RalfJung:incomplete-unsound, r=petrochenkov2020-05-16T17:46:29+00:00Ralf Jungpost@ralfj.de2020-05-16T17:46:29+00:00urn:sha1:aecab5e603ad0a904f2f357470b419b2ac6014d8
Incomplete features can also be unsound
Some incomplete features do not just ICE, they are also currently unsound (e.g. https://github.com/rust-lang/rust/pull/72029, and also `specialization` -- which is not yet marked incomplete but [should be](https://github.com/rust-lang/rust/pull/71420)). This makes the message reflect that.
While at it I also added a link to the tracking issue, which hopefully should explain what is incomplete/unsound about the feature.
Fix disagreeement about CGU reuse and LTO2020-05-10T02:30:48+00:00Alex Crichtonalex@alexcrichton.com2020-05-08T16:27:59+00:00urn:sha1:c7bd5a635ebef6520a2d7373973726b034345026
This commit fixes an issue where the codegen backend's selection of LTO
disagreed with what the codegen later thought was being done. Discovered
in #72006 we have a longstanding issue where if `-Clinker-plugin-lto` in
optimized mode is compiled incrementally it will always panic on the
second compilation. The underlying issue turned out to be that the
production of the original artifact determined that LTO should not be
done (because it's being postponed to the linker) but the CGU reuse
selection thought that LTO was done so it was trying to load pre-LTO
artifacts which were never generated.
The fix here is to ensure that the logic when generating code which
determines what kind of LTO is being done is shared amongst the CGU
reuse decision and the backend actually doing LTO. This means that
they'll both be in agreement about whether the previous compilation did
indeed produce incremental pre-LTO artifacts.
Closes #72006
adjust tests2020-05-09T12:40:17+00:00Ralf Jungpost@ralfj.de2020-04-22T08:21:32+00:00urn:sha1:6a8cf4a17c2d2b3daca27e787f4154e233ab4545Moving more build-pass tests to check-pass2020-04-24T03:21:38+00:00Val Markovicval@markovic.io2020-04-20T00:27:28+00:00urn:sha1:2155adbc3aeb4b38466a7127a7f4e92a8f8fc4e5
One or two tests became build-pass without the FIXME because they really
needed build-pass (were failing without it).
Helps with #62277
const prop: don't special case return place2020-04-20T19:18:20+00:00Jonas Schievinkjonasschievink@gmail.com2020-04-19T12:25:07+00:00urn:sha1:415fd0cc1a9bb902a2b4a22669debac74373cf67Tests.2020-04-14T14:52:19+00:00Felix S. Klock IIpnkfelix@pnkfx.org2020-04-14T14:52:19+00:00urn:sha1:12207f6c66f6fa5a19790c9c8bf1b398a7dc263d
Namely, a regression test for issue #69798 (export added), and the inverse of
that test (export removd).
update tests2020-03-31T17:01:49+00:00Bastian Kauschkebastian_kauschke@hotmail.de2020-03-27T20:56:19+00:00urn:sha1:698b20eedaff60aaed3b1f0bd1bec7d8c095f6a4