* 3.11.0 is a feature release with many improvements and the usual
collection of bug fixes.
- replace gcc-version.patch with gcc5.patch: This is the upstream
version
- drop valgrind-linux-4.0.patch: merged upstream
- add svn-r15766.patch: Fix valgrind with recent kernels
- jit-register-unregister.diff commented out, needs porting
OBS-URL: https://build.opensuse.org/package/show/devel:tools/valgrind?expand=0&rev=134
* Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port
is mostly complete, and is usable, but some SIMD instructions are as
yet unsupported.
* Support for little-endian variant of the 64-bit POWER architecture.
* Support for Android on MIPS32.
* Support for 64bit FPU on MIPS32 platforms.
* Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9.
* Configuration for and running on Android targets has changed.
See README.android in the source tree for details.
- drop VEX-r2803.diff, VEX-r2808.diff, VEX-r2816.diff, VEX-r2858.diff,
VEX-r2904.diff, VEX-r2910.diff, VEX-r2914.diff, VEX-r2915.diff,
VEX-r2916.diff, aarch64-VEX-support.diff, aarch64-support.diff,
r13767.diff, r13770.diff, r14184.diff, r14238.diff, r14239.diff,
r14240.diff, r14246.diff, r2798.diff, valgrind-r13948.diff
OBS-URL: https://build.opensuse.org/package/show/devel:tools/valgrind?expand=0&rev=119
- update to 3.9.0:
* Support for Intel AVX2 instructions. This is available only on 64
bit code.
* Support for POWER8 (Power ISA 2.07) instructions.
* Initial support for Intel Transactional Synchronization Extensions,
both RTM and HLE.
* Initial support for Hardware Transactional Memory on POWER.
* Improvements in handling of vectorised code, leading to
significantly fewer false error reports. You need to use the flag
--partial-loads-ok=yes to get the benefits of these changes.
* Better control over the leak checker. It is now possible to
specify which leak kinds (definite/indirect/possible/reachable)
should be displayed.
* Reduced "possible leak" reports from the leak checker by the use
of better heuristics.
* Better control of stacktrace acquisition for heap-allocated
blocks.
* Better reporting of leak suppression usage.
* New and modified GDB server monitor features.
* New flag --sigill-diagnostics to control whether a diagnostic
message is printed when the JIT encounters an instruction it can't
translate.
* The maximum amount of memory that Valgrind can use on 64 bit
targets has been increased from 32GB to 64GB.
* Additional smaller new features and many bug fixes.
- Remove obsolete raise-segnames-limit.diff,
valgrind-glibc-2.17.patch and valgrind-glibc-2.18.patch.
OBS-URL: https://build.opensuse.org/request/show/206037
OBS-URL: https://build.opensuse.org/package/show/devel:tools/valgrind?expand=0&rev=96
* Support for MIPS32 platforms running Linux. Valgrind has been
tested on MIPS32 and MIPS32r2 platforms running different Debian
Squeeze and MeeGo distributions. Both little-endian and big-endian
cores are supported. The tools Memcheck, Massif and Lackey have
been tested and are known to work. See README.mips for more details.
* Preliminary support for Android running on x86.
* Preliminary (as-yet largely unusable) support for MacOSX 10.8.
* Support for Intel AVX instructions and for AES instructions. This
support is available only for 64 bit code.
* Support for POWER Decimal Floating Point instructions.
* Non-libc malloc implementations are now supported. This is useful
for tools that replace malloc (Memcheck, Massif, DRD, Helgrind).
Using the new option --soname-synonyms, such tools can be informed
that the malloc implementation is either linked statically into the
executable, or is present in some other shared library different
from libc.so. This makes it possible to process statically linked
programs, and programs using other malloc libraries, for example
TCMalloc or JEMalloc.
* For tools that provide their own replacement for malloc et al, the
option --redzone-size=<number> allows users to specify the size of
the padding blocks (redzones) added before and after each client
allocated block. Smaller redzones decrease the memory needed by
Valgrind. Bigger redzones increase the chance to detect blocks
overrun or underrun. Prior to this change, the redzone size was
hardwired to 16 bytes in Memcheck.
* Memcheck:
- The leak_check GDB server monitor command now can
control the maximum nr of loss records to output.
- Reduction of memory use for applications allocating
OBS-URL: https://build.opensuse.org/package/show/devel:tools/valgrind?expand=0&rev=79
