Re: [Valgrind-developers] Valgrind-3.25.0.RC2 is available for testing

[P J. <Jee...@ib...>]

Hi Everyone,
valgrind-3.25.0.RC2 also looks good on Power and that there are no issues requiring fixes before releasing .

The PowerPC testsults for Both LE & BE are as follows

Powerpc64LE Results:

Power8:
There are no new failures compared to valgrind-3.25.0.RC1.

== 768 tests, 3 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 3 post failures ==
memcheck/tests/leak_cpp_interior         (stderr)
memcheck/tests/linux/rfcomm              (stderr)
memcheck/tests/linux/sys-execveat        (stderr)
massif/tests/bug469146                   (post)
massif/tests/new-cpp                     (post)
massif/tests/overloaded-new              (post)


Power9:
There are no new failures compared to valgrind-3.25.0.RC1.

== 775 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
memcheck/tests/linux/rfcomm              (stderr)


Power10:
There are no new failures compared to valgrind-3.25.0.RC1.

== 781 tests, 7 stderr failures, 2 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
memcheck/tests/execve1                   (stderr)
memcheck/tests/execve2                   (stderr)
memcheck/tests/linux/rfcomm              (stderr)
memcheck/tests/thread_alloca             (stderr)
helgrind/tests/getaddrinfo               (stderr)
drd/tests/getaddrinfo                    (stderr)
none/tests/allexec32                     (stdout)
none/tests/allexec64                     (stdout)
none/tests/scripts/shell                 (stderr)


PowerpcBE Results:

Power8:
There are no new failures compared to valgrind-3.25.0.RC1.

== 785 tests, 333 stderr failures, 70 stdout failures, 3 stderrB failures, 3 stdoutB failures, 6 post failures ==

Power9:
There are no new failures compared to valgrind-3.25.0.RC1

== 819 tests, 52 stderr failures, 45 stdout failures, 1 stderrB failure, 2 stdoutB failures, 2 post failures ==

Thanks,
Jeevitha


From: Mark Wielaard <ma...@kl...>
Date: Thursday, 24 April 2025 at 7:31 AM
To: val...@li... <val...@li...>, val...@li... <val...@li...>
Subject: [EXTERNAL] [Valgrind-developers] Valgrind-3.25.0.RC2 is available for testing
An RC2 tarball for 3.25.0 is now available at
https://sourceware.org/pub/valgrind/valgrind-3.25.0.RC2.tar.bz2 
(md5sum = 4e53a0a1a8d1404e77e6c45015eeb472)
(sha1sum = ba482eeeb89dd271006f59b09f01048be6530a53)
https://sourceware.org/pub/valgrind/valgrind-3.25.0.RC2.tar.bz2.asc 

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 

Changes from RC1:

Florian Krohm (2):
  s390x: Fix a comment
  s390x only: Clean up unused Ijk_... values

Mark Wielaard (4):
  auxprogs/Makefile.am (EXTRA_DIST): Add ltpchecks helper files
  Update NEWS for RISCV64/Linux and --modify-fds=[no|high] option
  none/tests/riscv64/testinst.h: Use lla instead of la in JMP_RANGE
  Set version to 3.25.0-RC2

Paul Floyd (8):
  Bug 502871 - Make Helgrind "pthread_cond_{signal,broadcast}: dubious: associated lock is not held by any thread" optional
  Add 3.25 highlights to NEWS for FreeBSD.
  Doc: add description of cond signal without mutex lock.
  Helgrind regtest: use --check-cond-signal-mutex=yes in tc20_verifywrap
  FreeBSD regtest: add auxv_script to dist_noinst_SCRIPTS
  Illumos suppression and regtest
  Illumos regtest: add an expected for none/tests/fdleak_socketpair_xml.stderr
  Regtest: clean up warning and compilation of bug290061.c

Petr Pavlu (4):
  riscv64: Fix tests compilation with newer GNU as
  riscv64: Merge decoding of csrrw and csrrs
  riscv64: Add support for csrrc
  riscv64: Drop the not-needed type for FpCSEL

zhaomingxin (1):
  riscv64: Add missing floating-point ITE/CSEL support in VEX backend

Unless a showstopper bug pops up 3.25.0 final will be released on
Fri Apr 27.


_______________________________________________
Valgrind-developers mailing list
Val...@li...
https://lists.sourceforge.net/lists/listinfo/valgrind-developers