bors d150dbb067 Auto merge of #113708 - rcvalle:rust-cfi-fix-100778, r=compiler-errors
CFI: Fix ICE: encode_const: unexpected type [usize

Fixes #100778 and #113366, and complements #106547 by adding support for encoding const parameters.
2023-07-27 02:48:38 +00:00
..
2023-03-20 10:25:29 +00:00
2023-07-08 15:38:40 +02:00
2023-01-17 16:23:22 +01:00
2023-07-08 15:38:40 +02:00
2023-07-08 15:38:40 +02:00
2023-01-11 20:42:13 -05:00
2023-01-17 16:23:22 +01:00
2023-01-17 16:23:22 +01:00
2023-03-16 15:07:04 +01:00
2023-07-08 15:38:40 +02:00
2023-05-03 22:09:33 -07:00
2023-01-17 16:23:22 +01:00
2023-07-08 15:38:40 +02:00
2023-05-11 14:35:10 +00:00
2023-06-10 08:31:06 +00:00
2023-07-08 15:38:40 +02:00
2023-06-10 16:58:51 +00:00
2023-07-08 15:38:40 +02:00
2023-01-17 16:23:22 +01:00
2023-04-30 00:06:26 +08:00
2023-01-17 16:23:22 +01:00
2023-07-19 09:59:12 +00:00
2023-01-17 16:23:22 +01:00
2023-05-08 03:55:41 -07:00
2023-04-17 09:16:07 +02:00
2023-01-17 16:23:22 +01:00
2023-01-17 16:23:22 +01:00
2023-01-17 16:23:22 +01:00
2023-01-17 16:23:22 +01:00
2023-07-10 16:01:18 +00:00
2023-07-08 15:38:40 +02:00
2023-07-08 15:38:40 +02:00
2023-07-08 15:38:40 +02:00
2023-01-17 16:23:22 +01: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