许杰友 Jieyou Xu (Joe) aaca9fa482 compiletest: don't register MSVC/NONMSVC FileCheck prefixes
This was fragile as it was based on host target passed to compiletest,
but the user could cross-compile and run test for a different target
(e.g. cross from linux to msvc, but msvc won't be set on the target).
Furthermore, it was also very surprising as normally revision names
(other than `CHECK`) was accepted as FileCheck prefixes.
2024-12-19 20:36:51 +08:00
..
2024-10-06 18:12:25 +02:00
2024-11-17 21:49:10 +01:00
2024-09-09 19:39:43 -07:00
2024-09-09 19:39:43 -07:00
2024-08-29 18:12:31 +08:00
2024-11-17 21:49:10 +01:00
2024-09-09 19:39:43 -07:00
2024-06-16 17:19:25 +08:00
2024-07-14 13:48:29 +03:00
2024-07-14 13:48:29 +03:00
2024-12-10 21:41:05 +01:00
2024-07-14 13:48:29 +03:00
2024-10-22 02:25:38 -07:00
2024-08-07 00:41:48 -04:00
2024-06-19 21:26:48 +01:00
2024-09-09 19:39:43 -07: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