Files
rust/tests/codegen-llvm
Jonathan Brouwer 04873a08af Rollup merge of #156878 - qaijuang:sve-tuple-intrinsics-filecheck, r=workingjubilee
codegen: re-enable FileCheck for scalable-vector tuple intrinsics

The FileCheck directives in `tests/codegen-llvm/scalable-vectors/tuple-intrinsics.rs` were not actually being checked: the test used `//@ build-pass`, and rust-lang/rust#155630 made that explicit by replacing it with `//@ skip-filecheck`.

This fixes the stale checks and re-enables FileCheck for the test. The `get` and `set` cases now use concrete index-0 wrappers, so they have stable `#[no_mangle]` names for FileCheck to match.

Fixes rust-lang/rust#155665.

r? @jieyouxu
2026-05-25 20:54:08 +02: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