From f40b2e7be5bba58ee021211e872426262a093000 Mon Sep 17 00:00:00 2001 From: Xi Ruoyao Date: Wed, 2 Aug 2023 14:02:08 +0800 Subject: gcc: Document new test failures with Glibc-2.38 Well, the analyzer failures are introduced by literally *my* Glibc change [1] and I'll sort them out for GCC 14... And the ASAN failures seem caused by the introduction of __isoc23_strtol (the libsanitizer does not know to intercept it). I'll test with LLVM once I reach it in BLFS (LLVM is the upstream of libsanitizer) and make a bug report. limits-exprparen.c also fails to me, it needs "ulimit -s 65536" instead of "ulimit -s 32768" in my build but maybe it's caused by my custom *FLAGS. [1]:https://sourceware.org/git/?p=glibc.git;a=commit;h=71d9e0fe766a --- chapter08/gcc.xml | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'chapter08') diff --git a/chapter08/gcc.xml b/chapter08/gcc.xml index bb22fbca5..0c4f591f2 100644 --- a/chapter08/gcc.xml +++ b/chapter08/gcc.xml @@ -184,6 +184,16 @@ su tester -c "PATH=$PATH make -k check" vect directory are known to fail if the hardware does not support AVX. + + With Glibc-2.38, the analyzer tests named + data-model-4.c and + conftest-1.c are known to fail. + In the asan tests, the subtest named + AddressSanitizer_StrtolOOBTest in the test + asan_test.C and the test named + interception-malloc-test-1.C are known to fail. + + A few unexpected failures cannot always be avoided. The GCC developers are usually aware of these issues, but have not resolved them yet. Unless the test results are vastly different from those at the above URL, -- cgit v1.2.3-54-g00ecf