diff options
| author | León Orell Valerian Liehr <me@fmease.dev> | 2025-05-11 02:44:40 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-05-11 02:44:40 +0200 |
| commit | 615b4479741e6e5b182ea1f3dd7486511c681654 (patch) | |
| tree | e82e85883479dbbf8de305b3627103d9f4202bdb /compiler/rustc_mir_transform/src/coverage/counters.rs | |
| parent | f96f4814a914f3f5684089263341e2cbffce0612 (diff) | |
| parent | 6814c38da20ddfb887b7763475edb3ac0ed55a64 (diff) | |
| download | rust-615b4479741e6e5b182ea1f3dd7486511c681654.tar.gz rust-615b4479741e6e5b182ea1f3dd7486511c681654.zip | |
Rollup merge of #140903 - RalfJung:fallback-body-tests, r=WaffleLapkin
test intrinsic fallback bodies with Miri `@Urgau` noted in https://github.com/rust-lang/rust/pull/140792 that fallback bodies our backends don't use are untested... which is correct, and it is a problem. So this adds a testing-only flag to Miri to force the use of fallback bodies, and adds a run of the Miri test suite with that flag to CI. This should not take much more than a minute so I hope it's fine? Let's see how long it actually takes. While at it, I made that test run also enable MIR optimizations. Miri's CI has a run with that, and it has caught mir-opt bugs in the past -- this way we'd see the CI failure earlier. r? `@scottmcm`
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/counters.rs')
0 files changed, 0 insertions, 0 deletions