Files
rust/src/test/codegen
Nicholas Bishop 54d9ba8239 Use RelocModel::Pic for UEFI targets
In https://github.com/rust-lang/rust/pull/100537, the relocation model
for UEFI targets was changed from PIC (the default value) to
static. There was some dicussion of this change here:
https://github.com/rust-lang/rust/pull/100537#discussion_r952363012

It turns out that this can cause compilation to fail as described in
https://github.com/rust-lang/rust/issues/101377, so switch back to PIC.

Fixes https://github.com/rust-lang/rust/issues/101377
2022-09-09 15:26:19 -04:00
..
2022-08-27 16:50:41 +03:00
2022-07-01 17:45:13 +02:00
2022-08-31 18:24:55 +08:00
2018-12-25 21:08:33 -07:00
2022-05-17 07:11:29 -04:00
2021-12-12 11:20:03 +00:00
2021-12-12 11:20:03 +00:00
2020-01-07 21:28:22 +01:00
2021-03-14 01:46:00 +09:00
2018-12-25 21:08:33 -07:00
2022-02-19 17:29:56 +00:00
2018-12-25 21:08:33 -07:00
2018-12-25 21:08:33 -07:00
2017-04-12 19:12:50 -05:00
2022-07-07 09:27:44 +02:00
2021-12-12 11:20:03 +00:00
2018-12-25 21:08:33 -07:00
2018-12-25 21:08:33 -07:00
2018-12-25 21:08:33 -07:00
2018-12-25 21:08:33 -07:00
2022-08-31 18:24:55 +08:00
2020-02-08 18:47:41 -05:00
2018-12-25 21:08:33 -07:00
2022-07-01 17:45:13 +02:00
2022-06-15 18:38:26 -07:00
2018-12-25 21:08:33 -07:00
2018-12-25 21:08:33 -07:00
2018-12-25 21:08:33 -07:00
2021-08-03 07:59:59 -07:00
2022-05-13 12:08:54 -07:00
2019-04-22 16:57:01 +01:00
2022-04-20 09:25:47 +02:00
2018-12-25 21:08:33 -07:00
2022-07-01 17:45:13 +02:00
2022-07-01 17:45:13 +02:00
2022-08-31 18:24:55 +08:00
2022-07-01 17:45:13 +02:00
2018-12-25 21:08:33 -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