valgrind-3.14.0

[Douglas R. Reno]

New minor version

Extreme caution needs to be exercised with this update. I've had it make my system hardlock before during the tests, as it seems to have code that is highly dependent on corner-cases in glibc being available when it's built.

[Bruce Dubbs]

Release 3.14.0 (9 October 2018) 3.14.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. There is also preliminary support for X86/macOS 10.13, AMD64/macOS 10.13.

• ==================== CORE CHANGES ===================

• The new option --keep-debuginfo=no|yes (default no) can be used to retain debug info for unloaded code. This allows saved stack traces (e.g. for memory leaks) to include file/line info for code that has been dlclose'd (or similar). See the user manual for more information and known limitations.

• Ability to specify suppressions based on source file name and line number.

• Majorly overhauled register allocator. No end-user changes, but the JIT generates code a bit more quickly now.

• ================== PLATFORM CHANGES =================

• Preliminary support for macOS 10.13 has been added.

• mips: support for MIPS32/MIPS64 Revision 6 has been added.

• mips: support for MIPS SIMD architecture (MSA) has been added.

• mips: support for MIPS N32 ABI has been added.

• s390: partial support for vector instructions (integer and string) has been added.

• ==================== TOOL CHANGES ====================

• Helgrind: Addition of a flag --delta-stacktrace=no|yes [yes on linux amd64/x86] which specifies how full history stack traces should be computed. Setting this to =yes can speed up Helgrind by 25% when using --history-level=full.

• Memcheck: reduced false positive rate for optimised code created by Clang 6 / LLVM 6 on x86, amd64 and arm64. In particular, Memcheck analyses code blocks more carefully to determine where it can avoid expensive definedness checks without loss of precision. This is controlled by the flag --expensive-definedness-checks=no|auto|yes [auto].

• ==================== OTHER CHANGES ====================

• Valgrind is now buildable with link-time optimisation (LTO). A new configure option --enable-lto=yes allows building Valgrind with LTO. If the toolchain supports it, this produces a smaller/faster Valgrind (up to 10%). Note that if you are doing Valgrind development, --enable-lto=yes massively slows down the build process.

[Bruce Dubbs]

Fixed at revision 20631.