diff options
| author | bors <bors@rust-lang.org> | 2024-06-15 00:04:01 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-06-15 00:04:01 +0000 |
| commit | 3fc81daffd18aa1fc00a1d67cfaca12a32a07e46 (patch) | |
| tree | 5f92b09d596845506470e36bcc30069612a1837e /compiler/rustc_ty_utils/src/instance.rs | |
| parent | f8e566053207b4ecbcbc7a7d6ded82c43061e3da (diff) | |
| parent | 186d94dc6be108d7e507e4a5129375335149cd23 (diff) | |
| download | rust-3fc81daffd18aa1fc00a1d67cfaca12a32a07e46.tar.gz rust-3fc81daffd18aa1fc00a1d67cfaca12a32a07e46.zip | |
Auto merge of #122613 - Zalathar:profiler, r=nnethercote
Don't build a broken/untested profiler runtime on mingw targets Context: https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/Why.20build.20a.20broken.2Funtested.20profiler.20runtime.20on.20mingw.3F #75872 added `--enable-profiler` to the `x86_64-mingw` job (to cause some additional tests to run), but had to also add `//@ ignore-windows-gnu` to all of the tests that rely on the profiler runtime actually *working*, because it's broken on that target. We can achieve a similar outcome by going through all the `//@ needs-profiler-support` tests that don't actually need to produce/run a binary, and making them use `-Zno-profiler-runtime` instead, so that they can run even in configurations that don't have the profiler runtime available. Then we can remove `--enable-profiler` from `x86_64-mingw`, and still get the same amount of testing. This PR also removes `--enable-profiler` from the mingw dist builds, since it is broken/untested on that target. Those builds have had that flag for a very long time.
Diffstat (limited to 'compiler/rustc_ty_utils/src/instance.rs')
0 files changed, 0 insertions, 0 deletions