Files
rust/tests/codegen-llvm
bors 1d59f669f9 Auto merge of #156849 - saethlin:test-call-site-inline-attributes, r=dianqk
Re-add call site inlining attributes

It is very odd that we are blindly setting the call site attributes to the same as the definition, because I think the point of the call site attributes is to differentiate between calls. Probably worth looking into later, but for now I think we should just be undoing the change we made by mistake.

This fixes the accidental regression from https://github.com/rust-lang/rust/pull/156242
2026-05-24 13:02:42 +00:00
..
2025-11-08 10:57:35 -07:00
2026-04-25 14:57:23 -07:00
2026-04-20 19:15:52 +02:00
2026-01-26 13:43:06 -06:00
2025-08-15 16:42:21 +00:00
2026-05-04 15:35:40 +02:00
2026-04-14 03:25:02 +05:30
2026-02-24 08:33:15 +00:00
2026-04-25 14:57:23 -07:00
2026-03-31 09:06:31 +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