Files
rust/tests/codegen
David Lattimore 42c0494499 Use Default visibility for rustc-generated C symbol declarations
Non-default visibilities should only be used for definitions, not
declarations, otherwise linking can fail.

Co-authored-by: Collin Baker <collinbaker@chromium.org>
2024-10-11 08:43:27 +11:00
..
2024-08-29 18:12:31 +08:00
2024-09-09 19:39:43 -07: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-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-09-09 13:29:47 +00:00
2024-07-14 13:48:29 +03:00
2024-08-07 00:41:48 -04:00
2024-09-09 19:39:43 -07: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