From: Mark Wielaard Date: Tue, 24 Dec 2024 18:11:17 +0000 (+0100) Subject: memcheck/tests/sh-mem-random.c: Set huge_addr to 240GB X-Git-Tag: VALGRIND_3_25_0~186 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=738af55f1b12a06f76943ca4afb9ba9ec3603ea5;p=thirdparty%2Fvalgrind.git memcheck/tests/sh-mem-random.c: Set huge_addr to 240GB https://www.kernel.org/doc/html/next/riscv/vm-layout.html Says RISC-V Linux Kernel SV39 user-space virtual memory ends at 256GB. So try at 240GB. This seems a reasonable value for other arches too. https://bugs.kde.org/show_bug.cgi?id=468575#c78 --- diff --git a/memcheck/tests/sh-mem-random.c b/memcheck/tests/sh-mem-random.c index ae82248ae..0e01684ac 100644 --- a/memcheck/tests/sh-mem-random.c +++ b/memcheck/tests/sh-mem-random.c @@ -247,7 +247,10 @@ int main(void) int nbytes_p; // (U1*)(UWord)constULL funny casting to keep gcc quiet on // 32-bit platforms - U1* huge_addr = (U1*)(UWord)0x6600000000ULL; // 408GB + // https://www.kernel.org/doc/html/next/riscv/vm-layout.html + // Says RISC-V Linux Kernel SV39 user-space virtual memory + // ends at 256GB. So try at 240GB. + U1* huge_addr = (U1*)(UWord)0x3c00000000ULL; // 240GB // Note, kernel 2.6.? on Athlon64 refuses fixed mmap requests // at above 512GB.