Update.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15640 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/NEWS b/NEWS
index f4dda77..ac8f520 100644
--- a/NEWS
+++ b/NEWS
@@ -7,18 +7,19 @@
This release supports X86/Linux, AMD64/Linux, ARM32/Linux,
ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux,
-MIPS32/Linux, MIPS64/Linux, TILEGX/Linux, ARM/Android, ARM64/Android,
-MIPS32/Android, X86/Android, X86/Solaris, AMD64/Solaris,
-X86/MacOSX 10.10 and 10.11 and AMD64/MacOSX 10.10 and 10.11.
+MIPS32/Linux, MIPS64/Linux, ARM/Android, ARM64/Android,
+MIPS32/Android, X86/Android, X86/Solaris, AMD64/Solaris, X86/MacOSX
+10.10 and AMD64/MacOSX 10.10. There is also preliminary support for
+X86/MacOSX 10.11, AMD64/MacOSX 10.11 and TILEGX/Linux.
* ================== PLATFORM CHANGES =================
-* Support for the Tilera TileGX architecture has been added.
-
* Support for Solaris/x86 and Solaris/amd64 has been added.
* Preliminary support for Mac OS X 10.11 (El Capitan) has been added.
+* Preliminary support for the Tilera TileGX architecture has been added.
+
* s390x: It is now required for the host to have the "long displacement"
facility. The oldest supported machine model is z990.
@@ -29,9 +30,16 @@
as a whole somewhat faster, so JIT-intensive activities, for example
program startup, are modestly faster, around 5%.
+* There have been changes to the default settings of several command
+ line flags, as detailed below.
+
+* Intel AVX2 support is more complete (64 bit targets only). On AVX2
+ capable hosts, the simulated CPUID will now indicate AVX2 support.
+
* ==================== TOOL CHANGES ====================
* Memcheck:
+
- The default value for --leak-check-heuristics has been changed from
"none" to "all". This helps to reduce the number of possibly
lost blocks, in particular for C++ applications.
@@ -39,8 +47,8 @@
- The default value for --keep-stacktraces has been changed from
"malloc-then-free" to "malloc-and-free". This has a small cost in
memory (one word per malloc-ed block) but allows Memcheck to show the
- 3 stacktraces of a dangling reference: Where the block was allocated,
- where it was freed, and where it is acccessed after free.
+ 3 stacktraces of a dangling reference: where the block was allocated,
+ where it was freed, and where it is acccessed after being freed.
- The default value for --partial-loads-ok has been changed from "no" to
"yes", so as to avoid false positive errors resulting from some kinds
@@ -54,25 +62,26 @@
- The 'block_list' monitor command has been enhanced:
o it can print a range of loss records
o it now accepts an optional argument 'limited <max_blocks>'
- to control the nr of block printed.
- o if a block has been found using an heuristic, then
+ to control the number of blocks printed.
+ o if a block has been found using a heuristic, then
'block_list' now shows the heuristic after the block size.
o the loss records/blocks to print can be limited to the blocks
found via specified heuristics.
- - The C helper functions used to instrument loads on x86-linux and
- arm-linux (both 32-bit only) have been replaced by handwritten
- assembly sequences. This gives speedups in the region of 0% to 7%
- for those targets only.
+ - The C helper functions used to instrument loads on
+ x86-{linux,solaris} and arm-linux (both 32-bit only) have been
+ replaced by handwritten assembly sequences. This gives speedups
+ in the region of 0% to 7% for those targets only.
- - New command line option: --expensive-definedness-checks=yes|no which
- is useful to avoid occasional invalid complaints on optimised code.
- Watchout for runtime degradation: 25% have been observed but, as always,
- this is highly application specific. The default setting is "no".
+ - A new command line option, --expensive-definedness-checks=yes|no,
+ which is useful to avoid occasional invalid uninitialised-value
+ errors in optimised code. Watch out for runtime degradation, as
+ this can be up to 25%. As always, though, the slowdown is highly
+ application specific. The default setting is "no".
* Massif:
- - New monitor command 'all_snapshots <filename>' that dumps all
+ - A new monitor command 'all_snapshots <filename>' dumps all
snapshots taken so far.
* Helgrind:
@@ -116,27 +125,27 @@
* When a process dies due to a signal, Valgrind now shows the signal
and the stacktrace at default verbosity (i.e. verbosity 1).
-* Address description logic (used by memcheck and helgrind)
- now describes addresses in anonymous segments, file mmap-ed
- segments, shared memory segments and the brk data segment.
+* The address description logic used by Memcheck and Helgrind now
+ describes addresses in anonymous segments, file mmap-ed segments,
+ shared memory segments and the brk data segment.
-* Option --error-markers=<begin>,<end> can be used to mark
- the begin/end of errors in textual output mode, to facilitate
- searching/extracting errors in output files mixing valgrind
- errors with program output.
+* The new option --error-markers=<begin>,<end> can be used to mark the
+ begin/end of errors in textual output mode, to facilitate
+ searching/extracting errors in output files that mix valgrind errors
+ with program output.
-* New option --max-threads=<number> can be used to change the number
+* The new option --max-threads=<number> can be used to change the number
of threads valgrind can handle. The default is 500 threads which
should be more than enough for most applications.
-* New option --valgrind-stacksize=<number> can be used to change the
+* The new option --valgrind-stacksize=<number> can be used to change the
size of the private thread stacks used by Valgrind. This is useful
for reducing memory use or increasing the stack size if Valgrind
segfaults due to stack overflow.
-* New option --avg-transtab-entry-size=<number> can be used to specify
+* The new option --avg-transtab-entry-size=<number> can be used to specify
the expected instrumented block size, either to reduce memory use or
- to avoid excess retranslations.
+ to avoid excessive retranslation.
* Valgrind can be built with Intel's ICC compiler, version 14.0 or later.
@@ -191,6 +200,7 @@
319274 Fix unhandled syscall: unix:410 (sigsuspend_nocancel) on OS X
324181 mmap does not handle MAP_32BIT (handle it now, rather than fail it)
327745 Fix valgrind 3.9.0 build fails on Mac OS X 10.6.8
+330147 libmpiwrap PMPI_Get_count returns undefined value
333051 mmap of huge pages fails due to incorrect alignment
== 339163
334802 valgrind does not always explain why a given option is bad
@@ -236,6 +246,7 @@
341698 Valgrind's AESKEYGENASSIST gives wrong result in words 0 and 2 [..]
341789 aarch64: shmat fails with valgrind on ARMv8
341997 MIPS64: Cavium OCTEON insns - immediate operand handled incorrectly
+342008 valgrind.h needs type cast [..] for clang/llvm in 64-bit mode
342038 Unhandled syscalls on aarch64 (mbind/get/set_mempolicy)
342063 wrong format specifier for test mcblocklistsearch in gdbserver_tests
342117 Hang when loading PDB file for MSVC compiled Firefox under Wine
@@ -359,6 +370,7 @@
350062 vex x86->IR: 0x66 0xF 0x3A 0xB (ROUNDSD) on OS X
350202 Add limited param to 'monitor block_list'
350290 s390x: Support instructions fixbr(a)
+350359 memcheck/tests/x86/fxsave hangs indefinetely on OS X
350809 Fix none/tests/async-sigs for Solaris
350811 Remove reference to --db-attach which has been removed.
350813 Memcheck/x86: enable handwritten assembly helpers for x86/Solaris too
@@ -372,6 +384,7 @@
351858 ldsoexec support on Solaris
351873 Newer gcc doesn't allow __builtin_tabortdc[i] in ppc32 mode
352130 helgrind reports false races for printfs using mempcpy on FILE* state
+352320 arm64 crash on none/tests/nestedfs
n-i-bz Provide implementations of certain compiler builtins to support
compilers that may not provide those
n-i-bz Old STABS code is still being compiled, but never used. Remove it.