Hello community, here is the log from the commit of package valgrind for openSUSE:Factory checked in at 2020-06-28 23:02:43 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/valgrind (Old) and /work/SRC/openSUSE:Factory/.valgrind.new.3060 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "valgrind" Sun Jun 28 23:02:43 2020 rev:126 rq:816789 version:3.16.0 Changes: -------- --- /work/SRC/openSUSE:Factory/valgrind/valgrind.changes 2020-05-13 22:58:59.419349468 +0200 +++ /work/SRC/openSUSE:Factory/.valgrind.new.3060/valgrind.changes 2020-06-28 23:02:58.238189990 +0200 @@ -1,0 +2,57 @@ +Fri Jun 19 08:14:24 UTC 2020 - Michal Suchanek <[email protected]> + +- Use autopatch + - Change armv6-support.diff to a/b format + +------------------------------------------------------------------- +Fri Jun 19 07:55:22 UTC 2020 - Dirk Mueller <[email protected]> + +- update to 3.16.0: + * Many bugfixes, too many to list here, see NEWS file + - The implicit memcpy done by each call to realloc now counts towards the + read and write counts of resized heap blocks, making those counts higher + and more accurate. + - cg_annotate's --auto and --show-percs options now default to 'yes', because + they are usually wanted. + - callgrind_annotate's --auto and --show-percs options now default to 'yes', + because they are usually wanted. + - The command option --collect-systime has been enhanced to specify + the unit used to record the elapsed time spent during system calls. + The command option now accepts the values no|yes|msec|usec|nsec, + where yes is a synonym of msec. When giving the value nsec, the + system cpu time of system calls is also recorded. + - Several memcheck options are now dynamically changeable. + Use valgrind --help-dyn-options to list them. + - The release 3.15 introduced a backward incompatible change for + some suppression entries related to preadv and pwritev syscalls. + When reading a suppression entry using the unsupported 3.14 format, + valgrind will now produce a warning to say the suppression entry will not + work, and suggest the needed change. + - Significantly fewer false positive errors on optimised code generated by + Clang and GCC. In particular, Memcheck now deals better with the + situation where the compiler will transform C-level "A && B" into "B && A" + under certain circumstances (in which the transformation is valid). + Handling of integer equality/non-equality checks on partially defined + values is also improved on some architectures. + - The exprimental Stack and Global Array Checking tool has been removed. + It only ever worked on x86 and amd64, and even on those it had a + high false positive rate and was slow. An alternative for detecting + stack and global array overruns is using the AddressSanitizer (ASAN) + facility of the GCC and Clang compilers, which require you to rebuild + your code with -fsanitize=address. + - Option -T tells vgdb to output a timestamp in the vgdb information messages. + - The gdbserver monitor commands that require an address and an optional + length argument now accepts the alternate 'C like' syntax "address[length]". + For example, the memcheck command "monitor who_points_at 0x12345678 120" + can now also be given as "monitor who_points_at 0x12345678[120]". + - 001-Add-newer-constants-for-prctl-syscall.patch + 0001-Fix-makefile-consistency-check.patch + 0001-s390x-Add-CPU-model-for-z15.patch + 0001-s390x-Add-models-z14-and-z14-ZR1.patch + 0001-s390x-Clean-up-s390-check-opcodes.pl.patch + 0001-Add-newer-constants-for-prctl-syscall.patch + 0002-Add-support-for-PR_CAPBSET_READ-and-_DROP-syscalls.patch: + dropped as those patches were from upstream and are already in 3.16.0 + - add 0001-Power-PC-Fix-extraction-of-the-L-field-for-sync-inst.patch (bsc#1173135) + +------------------------------------------------------------------- Old: ---- 0001-Add-newer-constants-for-prctl-syscall.patch 0001-Fix-makefile-consistency-check.patch 0001-s390x-Add-CPU-model-for-z15.patch 0001-s390x-Add-models-z14-and-z14-ZR1.patch 0001-s390x-Clean-up-s390-check-opcodes.pl.patch 0002-Add-support-for-PR_CAPBSET_READ-and-_DROP-syscalls.patch valgrind-3.15.0.tar.bz2 valgrind-client-headers-source.changes New: ---- 0001-Power-PC-Fix-extraction-of-the-L-field-for-sync-inst.patch valgrind-3.16.0.tar.bz2 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ valgrind.spec ++++++ --- /var/tmp/diff_new_pack.qllEcQ/_old 2020-06-28 23:03:03.302206808 +0200 +++ /var/tmp/diff_new_pack.qllEcQ/_new 2020-06-28 23:03:03.302206808 +0200 @@ -29,7 +29,7 @@ %bcond_without docs Name: valgrind%{?psuffix} -Version: 3.15.0 +Version: 3.16.0 Release: 0 Summary: Memory Management Debugger License: GPL-2.0-or-later AND GFDL-1.2-only @@ -39,15 +39,9 @@ # https://bugs.kde.org/show_bug.cgi?id=390553 # https://github.com/olafhering/valgrind/compare/olh-base-master...olh-fixes-master Patch0: valgrind.xen.patch +# PATCH-FIX-UPSTREAM 0001-Power-PC-Fix-extraction-of-the-L-field-for-sync-inst.patch +Patch1: 0001-Power-PC-Fix-extraction-of-the-L-field-for-sync-inst.patch Patch2: armv6-support.diff -# PATCH-FIX-UPSTREAM -Patch3: 0001-Add-newer-constants-for-prctl-syscall.patch -# PATCH-FIX-UPSTREAM -Patch4: 0002-Add-support-for-PR_CAPBSET_READ-and-_DROP-syscalls.patch -Patch5: 0001-Fix-makefile-consistency-check.patch -Patch6: 0001-s390x-Add-models-z14-and-z14-ZR1.patch -Patch7: 0001-s390x-Clean-up-s390-check-opcodes.pl.patch -Patch8: 0001-s390x-Add-CPU-model-for-z15.patch Patch9: parallel-lto.patch Patch10: dhat-use-datadir.patch %if "%{flavor}" == "" @@ -158,16 +152,7 @@ %prep %setup -q -n valgrind-%{version} -%patch0 -p1 -%patch2 -%patch3 -p1 -%patch4 -p1 -%patch5 -p1 -%patch6 -p1 -%patch7 -p1 -%patch8 -p1 -%patch9 -p1 -%patch10 -p1 +%autopatch -p1 %build %if "%{flavor}" == "" ++++++ 0001-Power-PC-Fix-extraction-of-the-L-field-for-sync-inst.patch ++++++ >From fb6f7abcbc92506d302fb18a2c5fc853d2929248 Mon Sep 17 00:00:00 2001 From: Carl Love <[email protected]> Date: Tue, 9 Jun 2020 10:42:03 -0500 Subject: [PATCH] Power PC Fix extraction of the L field for sync instruction The L field is currently a two bit[22:21] field in ISA 3.0. The size of the L field has changed over time. Currently the ISA 3.0 Valgrind sync instruction support code sets the flag_L for the instruction L field to a five bit value that includes bits that are marked reserved the sync instruction. This patch fixes the issue for ISA 3.0 to only setting flag_L the specified two bits. Valgrind bugzilla: https://bugs.kde.org/show_bug.cgi?id=422677 --- VEX/priv/guest_ppc_toIR.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/VEX/priv/guest_ppc_toIR.c b/VEX/priv/guest_ppc_toIR.c index 582c59ec0..c4965a19e 100644 --- a/VEX/priv/guest_ppc_toIR.c +++ b/VEX/priv/guest_ppc_toIR.c @@ -8777,7 +8777,7 @@ static Bool dis_memsync ( UInt theInstr ) /* X-Form, XL-Form */ UChar opc1 = ifieldOPC(theInstr); UInt b11to25 = IFIELD(theInstr, 11, 15); - UChar flag_L = ifieldRegDS(theInstr); + UChar flag_L = IFIELD(theInstr, 21, 2); //ISA 3.0 UInt b11to20 = IFIELD(theInstr, 11, 10); UInt M0 = IFIELD(theInstr, 11, 5); UChar rD_addr = ifieldRegDS(theInstr); -- 2.27.0 ++++++ armv6-support.diff ++++++ --- /var/tmp/diff_new_pack.qllEcQ/_old 2020-06-28 23:03:03.338206927 +0200 +++ /var/tmp/diff_new_pack.qllEcQ/_new 2020-06-28 23:03:03.338206927 +0200 @@ -1,7 +1,5 @@ -Index: configure.ac -=================================================================== ---- configure.ac.orig -+++ configure.ac +--- a/configure.ac ++++ b/configure.ac @@ -252,7 +252,7 @@ case "${host_cpu}" in ARCH_MAX="s390x" ;; ++++++ valgrind-3.15.0.tar.bz2 -> valgrind-3.16.0.tar.bz2 ++++++ /work/SRC/openSUSE:Factory/valgrind/valgrind-3.15.0.tar.bz2 /work/SRC/openSUSE:Factory/.valgrind.new.3060/valgrind-3.16.0.tar.bz2 differ: char 11, line 1 ++++++ valgrind.xen.patch ++++++ ++++ 3463 lines (skipped) ++++ between /work/SRC/openSUSE:Factory/valgrind/valgrind.xen.patch ++++ and /work/SRC/openSUSE:Factory/.valgrind.new.3060/valgrind.xen.patch
