[pkgsrc/trunk]: pkgsrc/devel/valgrind Update devel/valgrind to version 3.13.0.

[alnsn <alnsn%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/337971023489
branches:  trunk
changeset: 374818:337971023489
user:      alnsn <alnsn%pkgsrc.org@localhost>
date:      Mon Jan 29 22:35:06 2018 +0000

description:
Update devel/valgrind to version 3.13.0.

3.13.0 adds support for larger processes and programs, solidifies and improves
support on existing platforms, and provides new heap-use reporting facilities.

      Release 3.13.0 (15 June 2017)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

3.13.0 is a feature release with many improvements and the usual collection of
bug fixes.

This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux,
PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux,
MIPS64/Linux, ARM/Android, ARM64/Android, MIPS32/Android, X86/Android,
X86/Solaris, AMD64/Solaris and AMD64/MacOSX 10.12.

* ==================== CORE CHANGES ===================

* The translation cache size has been increased to keep up with the demands of
  large applications.  The maximum number of sectors has increased from 24 to
  48.  The default number of sectors has increased from 16 to 32 on all
  targets except Android, where the increase is from 6 to 12.

* The amount of memory that Valgrind can use has been increased from 64GB to
  128GB.  In particular this means your application can allocate up to about
  60GB when running on Memcheck.

* Valgrind's default load address has been changed from 0x3800'0000 to
  0x5800'0000, so as to make it possible to load larger executables.  This
  should make it possible to load executables of size at least 1200MB.

* A massive spaceleak caused by reading compressed debuginfo files has been
  fixed.  Valgrind should now be entirely usable with gcc-7.0 "-gz" created
  debuginfo.

* The C++ demangler has been updated.

* Support for demangling Rust symbols has been added.

* A new representation of stack traces, the "XTree", has been added.  An XTree
  is a tree of stacktraces with data associated with the stacktraces.  This is
  used by various tools (Memcheck, Helgrind, Massif) to report on the heap
  consumption of your program.  Reporting is controlled by the new options
  --xtree-memory=none|allocs|full and --xtree-memory-file=<file>.

  A report can also be produced on demand using the gdbserver monitor command
  'xtmemory [<filename>]>'.  The XTree can be output in 2 formats: 'callgrind
  format' and 'massif format. The existing visualisers for these formats (e.g.
  callgrind_annotate, KCachegrind, ms_print) can be used to visualise and
  analyse these reports.

  Memcheck can also produce XTree leak reports using the Callgrind file
  format.  For more details, see the user manual.

* ================== PLATFORM CHANGES =================

* ppc64: support for ISA 3.0B and various fixes for existing 3.0 support

* amd64: fixes for JIT failure problems on long AVX2 code blocks

* amd64 and x86: support for CET prefixes has been added

* arm32: a few missing ARMv8 instructions have been implemented

* arm64, mips64, mips32: an alternative implementation of Load-Linked and
  Store-Conditional instructions has been added.  This is to deal with
  processor implementations that implement the LL/SC specifications strictly
  and as a result cause Valgrind to hang in certain situations.  The
  alternative implementation is automatically enabled at startup, as required.
  You can use the option --sim-hints=fallback-llsc to force-enable it if you
  want.

* Support for OSX 10.12 has been improved.

* On Linux, clone handling has been improved to honour CLONE_VFORK that
  involves a child stack.  Note however that CLONE_VFORK | CLONE_VM is handled
  like CLONE_VFORK (by removing CLONE_VM), so applications that depend on
  CLONE_VM exact semantics will (still) not work.

* The TileGX/Linux port has been removed because it appears to be both unused
  and unsupported.

* ==================== TOOL CHANGES ====================

* Memcheck:

  - Memcheck should give fewer false positives when running optimised
    Clang/LLVM generated code.

  - Support for --xtree-memory and 'xtmemory [<filename>]>'.

  - New command line options --xtree-leak=no|yes and --xtree-leak-file=<file>
    to produce the end of execution leak report in a xtree callgrind format
    file.

  - New option 'xtleak' in the memcheck leak_check monitor command, to produce
    the leak report in an xtree file.

* Massif:

  - Support for --xtree-memory and 'xtmemory [<filename>]>'.

  - For some workloads (typically, for big applications), Massif memory
    consumption and CPU consumption has decreased significantly.

* Helgrind:

  - Support for --xtree-memory and 'xtmemory [<filename>]>'.

  - addition of client request VALGRIND_HG_GNAT_DEPENDENT_MASTER_JOIN, useful
    for Ada gnat compiled applications.

diffstat:

 devel/valgrind/Makefile |   8 ++++----
 devel/valgrind/PLIST    |   3 +--
 devel/valgrind/distinfo |  10 +++++-----
 3 files changed, 10 insertions(+), 11 deletions(-)

diffs (52 lines):

diff -r e0b372f4a632 -r 337971023489 devel/valgrind/Makefile
--- a/devel/valgrind/Makefile   Mon Jan 29 21:54:35 2018 +0000
+++ b/devel/valgrind/Makefile   Mon Jan 29 22:35:06 2018 +0000
@@ -1,12 +1,12 @@
-# $NetBSD: Makefile,v 1.25 2017/09/16 19:53:51 alnsn Exp $
+# $NetBSD: Makefile,v 1.26 2018/01/29 22:35:06 alnsn Exp $
 #
 
-DISTNAME=              valgrind-3.12.0
+DISTNAME=              valgrind-3.13.0
 CATEGORIES=            devel
-MASTER_SITES=          http://valgrind.org/downloads/
+MASTER_SITES=          ftp://sourceware.org/pub/valgrind/
 EXTRACT_SUFX=          .tar.bz2
 
-MAINTAINER=            pkgsrc-users%NetBSD.org@localhost
+MAINTAINER=            alnsn%NetBSD.org@localhost
 HOMEPAGE=              http://valgrind.org/
 COMMENT=               Debugging and profiling tools
 LICENSE=               gnu-gpl-v2
diff -r e0b372f4a632 -r 337971023489 devel/valgrind/PLIST
--- a/devel/valgrind/PLIST      Mon Jan 29 21:54:35 2018 +0000
+++ b/devel/valgrind/PLIST      Mon Jan 29 22:35:06 2018 +0000
@@ -1,4 +1,4 @@
-@comment $NetBSD: PLIST,v 1.9 2016/12/05 20:17:56 wiedi Exp $
+@comment $NetBSD: PLIST,v 1.10 2018/01/29 22:35:06 alnsn Exp $
 bin/callgrind_annotate
 bin/callgrind_control
 bin/cg_annotate
@@ -25,7 +25,6 @@
 include/valgrind/libvex_guest_ppc64.h
 include/valgrind/libvex_guest_s390x.h
 include/valgrind/libvex_guest_x86.h
-include/valgrind/libvex_guest_tilegx.h
 include/valgrind/libvex.h
 include/valgrind/libvex_ir.h
 include/valgrind/libvex_s390x_common.h
diff -r e0b372f4a632 -r 337971023489 devel/valgrind/distinfo
--- a/devel/valgrind/distinfo   Mon Jan 29 21:54:35 2018 +0000
+++ b/devel/valgrind/distinfo   Mon Jan 29 22:35:06 2018 +0000
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.9 2016/10/25 17:41:02 alnsn Exp $
+$NetBSD: distinfo,v 1.10 2018/01/29 22:35:06 alnsn Exp $
 
-SHA1 (valgrind-3.12.0.tar.bz2) = 7a6878bf998c60d1e377a4f22ebece8d9305bda4
-RMD160 (valgrind-3.12.0.tar.bz2) = 25d413bc0594bdf4d26ff19d031151a4dfe87920
-SHA512 (valgrind-3.12.0.tar.bz2) = 2c083f7c2e74dc58600397726d9d3af7a2cea40fe3d8733149886d1d77867e6c09996e5be1c58dd932f3662acf7363e04eeadbc0f9c8f0dac089e605024229be
-Size (valgrind-3.12.0.tar.bz2) = 12788556 bytes
+SHA1 (valgrind-3.13.0.tar.bz2) = ddf13e22dd0ee688bd533fc66b94cf88f75fad86
+RMD160 (valgrind-3.13.0.tar.bz2) = 809dcd3c656633cb9e1153eec491dce7d3e532c0
+SHA512 (valgrind-3.13.0.tar.bz2) = 34e1013cd3815d30a459b86220e871bb0a6209cc9e87af968f347083693779f022e986f211bdf1a5184ad7370cde12ff2cfca8099967ff94732970bd04a97009
+Size (valgrind-3.13.0.tar.bz2) = 14723076 bytes