Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing

2024-04-27 Thread Simon Sobisch
That's clang version 18.1.4 Target: aarch64-unknown-linux-android24 No flags set at all (other than --enable-lto). Checking for warning flags noted in config.log: CFLAGS_MPI='-g -O -fno-omit-frame-pointer -Wall -fpic' FLAG_W_CAST_ALIGN='-Wcast-align' FLAG_W_CAST_QUAL='-Wcast-qual' FLAG_W_EMPTY_

Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing

2024-04-27 Thread Paul Floyd via Valgrind-users
On 25-04-24 19:09, Simon Sobisch wrote: Am 25.04.2024 um 20:55 schrieb Paul Floyd via Valgrind-users: On 25-04-24 14:39, Simon Sobisch wrote: 3. compile warnings with clang on arm64 (in multiple files/positions with different arguments to the macros CALL_FN_W_W, CALL_FN_W_WW, CALL_FN_W_

Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing

2024-04-25 Thread Paul Floyd via Valgrind-users
On 24-04-24 23:33, Mark Wielaard wrote: An RC2 tarball for 3.23.0 is now available at FreeBSD amd64 and arm64 both still fine. A+ Paul ___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/lis

Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing

2024-04-25 Thread Simon Sobisch
Am 25.04.2024 um 20:55 schrieb Paul Floyd via Valgrind-users: On 25-04-24 14:39, Simon Sobisch wrote: 3. compile warnings with clang on arm64 (in multiple files/positions with different arguments to the macros CALL_FN_W_W, CALL_FN_W_WW, CALL_FN_W_WWW and CALL_FN_W_): For the arm64 wa

Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing

2024-04-25 Thread Paul Floyd via Valgrind-users
On 25-04-24 08:50, Simon Sobisch wrote: I've compiled and tried to run the RC2 on some environments, using 1. Find just a minor patch for configure.ac to improve help output and keep the style of the file (two missing spaces visible in "configure --help"; tabs/line breaks). 2. One thing th

Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing

2024-04-25 Thread Paul Floyd via Valgrind-users
On 25-04-24 14:39, Simon Sobisch wrote: 1. Several failing tests because of sed and ps usage. With 2.  Two failing tests on Debian with AMD Ryzen: 3. compile warnings with clang on arm64 (in multiple files/positions with different arguments to the macros CALL_FN_W_W, CALL_FN_W_WW, CALL_FN_

Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing

2024-04-25 Thread Carl Love via Valgrind-users
Mark: RC2 fixes a number of failures from RC1. I think it RC2 is good to go. Power 10 memcheck/tests/linux/rfcomm (stderr)Also failed for valgrind 3.22.0 Power 9 memcheck/tests/leak_cpp_interior (stderr)Also failed for valgrind 3.22.0 memcheck/tests/linux/rfcomm

Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing

2024-04-25 Thread Simon Sobisch
1. Several failing tests because of sed and ps usage. With sed --version This is not GNU sed version 4.0 BusyBox v1.35.0 (2022-11-19 10:13:10 UTC) multi-call binary. There are a bunch of sed: unsupported command , messages during "make regtest" so the result is not usable similar with

Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing

2024-04-25 Thread Simon Sobisch
I've compiled and tried to run the RC2 on some environments, using mkdir build cd build ../configure --enable-lto make -j8 make -j8 check make regtest make perf and think I've found some things related to the build system (and/or documentation). 1. Find just a minor patch for configure.ac to