Repository navigation
Get rid of the test-miri flag in config.toml #61833
Description
The test-miri flag changes whether -Zalways-encode-mir is passed to rustc, causing all metadata beyond stage 0 to include MIR of all functions, even private monomorphic ones. Instead, what we can do is to have miri tests first run cargo miri setup to generate that special libstd in CI in addition to the regular libstd. Then tests can be run with special libstd.
cc @RalfJung
Reacted by Mateusz Mikuła
Activity
RalfJung commentedon Jun 14, 2019
Worse, it also passes
--cfg mirito rustc, meaning we get the hashbrown without SIMD!RalfJung commentedon Jun 14, 2019
Oh also, ideally this could use or at least share some code with the build script Miri uses to do the same on its own CI.
EDIT: Or maybe not, that does some crazy
RUSTFLAGSstuff that probably should not be done for the released artifact.RalfJung commentedon Jul 31, 2019
I submitted a PR for this at #63162.
Rollup merge of rust-lang#63162 - RalfJung:miri-xargo, r=alexcrichton
Rollup merge of rust-lang#63162 - RalfJung:miri-xargo, r=alexcrichton