bors 1c44af9b79 Auto merge of #111836 - calebzulawski:target-feature-closure, r=workingjubilee
Fix #[inline(always)] on closures with target feature 1.1

Fixes #108655.  I think this is the most obvious solution that isn't overly complicated.  The comment includes more justification, but I think this is likely better than demoting the `#[inline(always)]` to `#[inline]`, since existing code is unaffected.
2023-07-23 00:16:03 +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-07-08 15:38:40 +02:00
2023-05-03 22:09:33 -07: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-04-30 00:06:26 +08:00
2023-07-19 09:59:12 +00:00
2023-05-08 03:55:41 -07:00
2023-04-17 09:16:07 +02: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

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