[libcxx][test] Fix a test for the range of file offsets on ARMv7 Linux targets.

[vvereschaka]

XFAIL the offset_range test on the ARMv7 Linux targets (32-bit).

Ref PR #122798

[llvmbot]

@llvm/pr-subscribers-libcxx

Author: Vladimir Vereschaka (vvereschaka)

Changes

XFAIL the offset_range test on the ARMv7 Linux targets (32-bit).

Ref PR #122798

---

Full diff: https://github.com/llvm/llvm-project/pull/123449.diff

1 Files Affected:

• (modified) libcxx/test/std/input.output/file.streams/fstreams/ifstream.members/offset_range.pass.cpp (+5)

diff --git a/libcxx/test/std/input.output/file.streams/fstreams/ifstream.members/offset_range.pass.cpp b/libcxx/test/std/input.output/file.streams/fstreams/ifstream.members/offset_range.pass.cpp
index 5afd4465db31e0..9bb52c8ac8f481 100644
--- a/libcxx/test/std/input.output/file.streams/fstreams/ifstream.members/offset_range.pass.cpp
+++ b/libcxx/test/std/input.output/file.streams/fstreams/ifstream.members/offset_range.pass.cpp
@@ -28,6 +28,11 @@
 //
 // XFAIL: target=powerpc-{{.+}}-aix{{.*}}
 
+// By default, off_t is typically a 32-bit integer on ARMv7 Linux systems, 
+// meaning it can represent file sizes up to 2GB (2^31 bytes) only.
+//
+// XFAIL: target=armv7{{.*}}-{{.+}}-linux{{.*}}
+
 #include <fstream>
 #include <iostream>
 #include <cassert>

[github-actions]

✅ With the latest revision this PR passed the C/C++ code formatter.

[mstorsjo]

This reasoning looks and sounds reasonable… however it doesn’t seem to hold universally, because we do have some existing CI test configurations that also run on armv7 Linux, where this test does pass. It didn’t trigger this XFAIL though, because the triple has a slightly different form - target=armv7l-linux-gnueabihf, so there’s no vendor field. If you’d tweak the regex to not require a vendor field, I think it would match - and this XFAIL would trigger…

Apparently that setup has got 64 bit off_t by default?