Re: Valgrind-3.22.0.RC2 is available for testing

Mark:

Valgrind-3.22.0.RC2 looks good on power. I have run the RC2 on Power
10LE, Power 9 LE, Power 8 LE/BE, and Power 7 BE. I see the two failures

memcheck/tests/bug340392                 (stderr)
memcheck/tests/linux/rfcomm              (stderr)

everywhere which is normal.  A couple of the older systems also report

memcheck/tests/leak_cpp_interior         (stderr)
memcheck/tests/linux/sys-execveat        (stderr)

which is also consistent on those platforms.

It all looks good on PowerPC.

                          Carl 

On Thu, 2023-10-26 at 14:48 +0200, Mark Wielaard wrote:
> An RC2 tarball for 3.22.0 is now available at
> https://sourceware.org/pub/valgrind/valgrind-3.22.0.RC2.tar.bz2
> (md5sum = 07bb18b0fd1c7347b350d8d71dc940f6)
> (sha1sum = 61c29e47efdc933ea3f23cb2f0fcebcd6d96dab1)
> https://sourceware.org/pub/valgrind/valgrind-3.22.0.RC2.tar.bz2.asc
> 
> Changes since RC1:
> 
> Andreas Arnez (5):
>       s390x: Fix memcheck false positives with certain comparisons
>       s390x regtest: Fix memcheck tests for cu21 and cu42 with Clang
>       Update NEWS to reflect Clang support for s390x
>       s390x: Adjust .gitignore after commit 7cf98163adb3f
>       s390x regtest: Activate 128 bit SIMD tests for s390x in vbit-
> test
> 
> Carl Love (3):
>       Bug 476025 - Powerpc, update expected results for the vbit-test
>       Revert "Bug 476025 - Powerpc, update expected results for the
> vbit-test"
>       Change the vbit test specification for Iop_CmpGT64Ux2
> 
> Mark Wielaard (7):
>       Add new drd/tests/thrd_create test to .gitignore
>       Add arm-linux build artifacts to .gitignore
>       vg_replace_malloc DELETE should not check size
>       Add 32bit variant of new_aligned_delete_default.stderr.exp
>       Add x86 variant of origin5-bz2.stderr.exp-glibc25-amd64-b
>       Add new exp files to EXTRA_DIST in memcheck/tests/Makefile.am
>       Set version to 3.22.0-RC2
> 
> Please give it a try in configurations that are important for you and
> report any problems you have, either on this mailing list, or
> (preferably) via our bug tracker at
> https://bugs.kde.org/enter_bug.cgi?product=valgrind
> 
> If nothing critical emerges, a final release will happen on Tuesday
> 31
> October.
> 
> 
> _______________________________________________
> Valgrind-developers mailing list
> Valgrind-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/valgrind-developers