about summary refs log tree commit diff
path: root/tests/codegen/instrument-coverage
AgeCommit message (Collapse)AuthorLines
2025-07-22Rename `tests/codegen` into `tests/codegen-llvm`Guillaume Gomez-161/+0
2024-12-11coverage: Adjust a codegen test to ignore the order of covmap/covfun globalsZalathar-4/+2
2024-08-07Disallow setting built-in cfgs via set the command-lineUrgau-15/+15
2024-06-14Use `-Zno-profiler-runtime` instead of `//@ needs-profiler-support`Zalathar-4/+5
For PGO/coverage tests that don't need to build or run an actual artifact, we can use `-Zno-profiler-runtime` to run the test even when the profiler runtime is not available.
2024-05-31Run rustfmt on `tests/codegen/`.Nicholas Nethercote-4/+2
Except for `simd-intrinsic/`, which has a lot of files containing multiple types like `u8x64` which really are better when hand-formatted. There is a surprising amount of two-space indenting in this directory. Non-trivial changes: - `rustfmt::skip` needed in `debug-column.rs` to preserve meaning of the test. - `rustfmt::skip` used in a few places where hand-formatting read more nicely: `enum/enum-match.rs` - Line number adjustments needed for the expected output of `debug-column.rs` and `coroutine-debug.rs`.
2024-05-28Make more of the test suite run on Mac CatalystMads Marquart-2/+2
This adds the `only-apple`/`ignore-apple` compiletest directive, and uses that basically everywhere instead of `only-macos`/`ignore-macos`. Some of the updates in `run-make` are a bit redundant, as they use `ignore-cross-compile` and won't run on iOS - but using Apple in these is still more correct, so I've made that change anyhow.
2024-05-04tests/ui: prepare some tests for --check-cfg by defaultUrgau-9/+6
2024-02-23Remove unhelpful `DEFINE_INTERNAL` from filecheck flagsZalathar-3/+2
This define was copied over from the run-make version of the test, but doesn't seem to serve any useful purpose.
2024-02-23Convert `tests/run-make/instrument-coverage` to an ordinary codegen testZalathar-0/+121
This test was already very close to being an ordinary codegen test, except that it needed some extra logic to set a few variables based on (target) platform characteristics. Now that we have support for `//@ filecheck-flags:`, we can instead set those variables using the normal test revisions mechanism.
2024-02-23Move existing coverage codegen tests into a subdirectoryZalathar-0/+47
This makes room for migrating over `tests/run-make/instrument-coverage`, without increasing the number of top-level items in the codegen test directory.