Files
Jonathan Brouwer b10b737aac Rollup merge of #159269 - fneddy:disable-test-rltf, r=folkertdev
disable range-len-try-from.rs on s390x

This optimisation is currently broken on s390x[^1]. It looks like a big-endian issue in general. but as we only know about the test fails on s390x we only disable it there.

Should be reenabled when the problem is fixed and llvm backend is updated.

[^1]: https://github.com/llvm/llvm-project/issues/208712
2026-07-14 16:49:11 +02:00
..
2025-11-08 10:57:35 -07:00
2026-06-26 13:24:12 +00:00
2026-06-15 00:56:07 +00:00
2026-06-04 15:19:24 +02:00
2026-07-13 10:54:53 +02:00
2026-06-04 15:19:24 +02:00
2025-08-15 16:42:21 +00:00
2026-06-15 19:52:50 +02:00
2026-07-13 10:54:53 +02:00
2026-07-13 10:54:53 +02:00
2026-06-04 15:19:24 +02:00
2026-05-04 15:35:40 +02:00
2026-04-14 03:25:02 +05:30
2026-06-04 15:19:24 +02:00
2026-02-24 08:33:15 +00:00
2026-07-13 10:14:58 -07:00
2026-07-13 10:14:58 -07:00
2026-04-25 14:57:23 -07:00
2026-06-04 15:19:24 +02:00
2026-03-31 09:06:31 +02:00
2026-07-13 10:54:53 +02:00
2026-06-04 15:19:24 +02:00
2026-06-05 20:19:51 +02:00
2026-07-07 17:31:05 +01:00
2026-06-02 19:56: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