diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2021-12-11 08:22:31 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-12-11 08:22:31 +0100 |
| commit | f7278cfc3c5a436d9e92d6eff3606b03f4459050 (patch) | |
| tree | b0c79e562f35243a3c4df335151f9c3eb19416a4 /compiler/rustc_mir_transform/src/coverage/tests.rs | |
| parent | d8bb4d69db35368cf3ceff92ee59b100339bce3b (diff) | |
| parent | ea68758299a89556e67f0bfffffb19c0c8346e8a (diff) | |
| download | rust-f7278cfc3c5a436d9e92d6eff3606b03f4459050.tar.gz rust-f7278cfc3c5a436d9e92d6eff3606b03f4459050.zip | |
Rollup merge of #91373 - djkoloski:fuchsia_test_suite, r=Mark-Simulacrum
Add needs-unwind to tests that depend on panicking These tests were found by running the test suite on fuchsia which compiles with `panic=abort` by default, then picking through the failures manually to locate the tests that require unwinding support. Most of these tests are already opted-out on platforms that compile with `panic=abort` by default. This just generalizes it a bit more so that fuchsia tests can be run properly. Currently, the `needs-unwind` directive needs to be manually passed to compiletest (e.g. via `--test-args '--target-panic=abort'`). Eventually, I would like `x.py` or compiletest to determine whether the directive should be used automatically based on the target panic settings.
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/tests.rs')
0 files changed, 0 insertions, 0 deletions