Files
rust/tests/codegen
Josh Stone 706f06c39a Use an explicit x86-64 cpu in tests that are sensitive to it
There are a few tests that depend on some target features **not** being
enabled by default, and usually they are correct with the default x86-64
target CPU. However, in downstream builds we have modified the default
to fit our distros -- `x86-64-v2` in RHEL 9 and `x86-64-v3` in RHEL 10
-- and the latter especially trips tests that expect not to have AVX.

These cases are few enough that we can just set them back explicitly.
2024-05-01 15:25:26 -07:00
..
2023-03-20 10:25:29 +00:00
2024-04-24 13:12:33 +01:00
2024-04-24 13:12:33 +01:00
2024-04-24 13:12:33 +01:00
2024-04-24 13:12:33 +01:00
2024-04-11 21:42:35 -04:00
2024-04-11 21:42:35 -04:00
2024-04-11 21:42:35 -04:00
2024-04-11 21:42:35 -04:00
2024-04-22 18:48:47 +02:00
2024-04-11 21:42:35 -04:00
2024-02-24 19:49:16 +00:00
2024-03-13 01:17:15 -04:00
2024-04-24 13:12:33 +01:00
2024-03-10 22:47:30 -04:00
2023-01-11 09:32:08 +00:00
2024-04-22 18:48:47 +02:00
2024-04-22 18:48:47 +02:00
2024-04-22 18:48:47 +02:00
2024-04-11 21:42:35 -04:00
2023-01-11 09:32:08 +00:00
2024-04-11 21:42:35 -04:00
2023-01-11 09:32:08 +00:00
2024-03-29 15:37:43 -07:00
2024-02-23 18:04:01 -05:00

The files here use the LLVM FileCheck framework, documented at https://llvm.org/docs/CommandGuide/FileCheck.html.

One extension worth noting is the use of revisions as custom prefixes for FileCheck. If your codegen test has different behavior based on the chosen target or different compiler flags that you want to exercise, you can use a revisions annotation, like so:

// revisions: aaa bbb
// [bbb] compile-flags: --flags-for-bbb

After specifying those variations, you can write different expected, or explicitly unexpected output by using <prefix>-SAME: and <prefix>-NOT:, like so:

// CHECK: expected code
// aaa-SAME: emitted-only-for-aaa
// aaa-NOT:                        emitted-only-for-bbb
// bbb-NOT:  emitted-only-for-aaa
// bbb-SAME:                       emitted-only-for-bbb