mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-04 02:18:37 +00:00
3a046ec1c1
For most memcheck users, no mempools are used, but the leak search logic was doing in any case special handling, leading to useless work such as sorting again an already sorted array and making a copy of an array without modifying it. This slightly optimises the perf reg tests of memcheck. perl perf/vg_perf --tools=memcheck --vg=. --vg=../trunk_untouched perf -- Running tests in perf ---------------------------------------------- -- bigcode1 -- bigcode1 . :0.08s me: 3.0s (38.1x, -----) bigcode1 trunk_untouched:0.08s me: 3.1s (38.6x, -1.3%) -- bigcode2 -- bigcode2 . :0.07s me: 7.4s (105.9x, -----) bigcode2 trunk_untouched:0.07s me: 7.5s (107.4x, -1.5%) -- bz2 -- bz2 . :0.40s me: 5.2s (12.9x, -----) bz2 trunk_untouched:0.40s me: 5.4s (13.6x, -5.0%) -- fbench -- fbench . :0.15s me: 2.8s (18.8x, -----) fbench trunk_untouched:0.15s me: 2.9s (19.0x, -1.1%) -- ffbench -- ffbench . :0.16s me: 2.7s (16.8x, -----) ffbench trunk_untouched:0.16s me: 2.7s (17.1x, -1.9%) -- heap -- heap . :0.06s me: 4.0s (66.5x, -----) heap trunk_untouched:0.06s me: 4.1s (68.7x, -3.3%) -- heap_pdb4 -- heap_pdb4 . :0.07s me: 6.2s (89.1x, -----) heap_pdb4 trunk_untouched:0.07s me: 6.6s (94.9x, -6.4%) -- many-loss-records -- many-loss-records . :0.01s me: 1.2s (122.0x, -----) many-loss-records trunk_untouched:0.01s me: 1.2s (125.0x, -2.5%) -- many-xpts -- many-xpts . :0.03s me: 1.2s (41.7x, -----) many-xpts trunk_untouched:0.03s me: 1.3s (43.7x, -4.8%) -- memrw -- memrw . :0.06s me: 1.2s (19.8x, -----) memrw trunk_untouched:0.06s me: 1.2s (20.2x, -1.7%) -- sarp -- sarp . :0.02s me: 1.8s (91.5x, -----) sarp trunk_untouched:0.02s me: 2.1s (103.5x,-13.1%) -- tinycc -- tinycc . :0.11s me: 7.1s (64.4x, -----) tinycc trunk_untouched:0.11s me: 7.1s (64.3x, 0.1%) -- Finished tests in perf ---------------------------------------------- == 12 programs, 24 timings =================
Release notes for Valgrind
~~~~~~~~~~~~~~~~~~~~~~~~~~
If you are building a binary package of Valgrind for distribution,
please read README_PACKAGERS. It contains some important information.
If you are developing Valgrind, please read README_DEVELOPERS. It contains
some useful information.
For instructions on how to build/install, see the end of this file.
If you have problems, consult the FAQ to see if there are workarounds.
Executive Summary
~~~~~~~~~~~~~~~~~
Valgrind is a framework for building dynamic analysis tools. There are
Valgrind tools that can automatically detect many memory management
and threading bugs, and profile your programs in detail. You can also
use Valgrind to build new tools.
The Valgrind distribution currently includes six production-quality
tools: a memory error detector, two thread error detectors, a cache
and branch-prediction profiler, a call-graph generating cache and
branch-prediction profiler, and a heap profiler. It also includes
three experimental tools: a heap/stack/global array overrun detector,
a different kind of heap profiler, and a SimPoint basic block vector
generator.
Valgrind is closely tied to details of the CPU, operating system and to
a lesser extent, compiler and basic C libraries. This makes it difficult
to make it portable. Nonetheless, it is available for the following
platforms:
- X86/Linux
- AMD64/Linux
- PPC32/Linux
- PPC64/Linux
- ARM/Linux
- ARM64/Linux
- x86/macOS
- AMD64/macOS
- S390X/Linux
- MIPS32/Linux
- MIPS64/Linux
- nanoMIPS/Linux
- X86/Solaris
- AMD64/Solaris
- X86/FreeBSD
- AMD64/FreeBSD
Note that AMD64 is just another name for x86_64, and Valgrind runs fine
on Intel processors. Also note that the core of macOS is called
"Darwin" and this name is used sometimes.
Valgrind is licensed under the GNU General Public License, version 2.
Read the file COPYING in the source distribution for details.
However: if you contribute code, you need to make it available as GPL
version 2 or later, and not 2-only.
Documentation
~~~~~~~~~~~~~
A comprehensive user guide is supplied. Point your browser at
$PREFIX/share/doc/valgrind/manual.html, where $PREFIX is whatever you
specified with --prefix= when building.
Building and installing it
~~~~~~~~~~~~~~~~~~~~~~~~~~
To install from the GIT repository:
0. Clone the code from GIT:
git clone https://sourceware.org/git/valgrind.git
There are further instructions at
http://www.valgrind.org/downloads/repository.html.
1. cd into the source directory.
2. Run ./autogen.sh to setup the environment (you need the standard
autoconf tools to do so).
3. Continue with the following instructions...
To install from a tar.bz2 distribution:
4. Run ./configure, with some options if you wish. The only interesting
one is the usual --prefix=/where/you/want/it/installed.
5. Run "make".
6. Run "make install", possibly as root if the destination permissions
require that.
7. See if it works. Try "valgrind ls -l". Either this works, or it
bombs out with some complaint. In that case, please let us know
(see http://valgrind.org/support/bug_reports.html).
Important! Do not move the valgrind installation into a place
different from that specified by --prefix at build time. This will
cause things to break in subtle ways, mostly when Valgrind handles
fork/exec calls.
The Valgrind Developers