alarsyo/spot
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

* HACKING: Add an example for using callgrind.

Browse source
This commit is contained in:
Alexandre Duret-Lutz 2011-04-09 10:56:12 +02:00
parent 0368d653ca
commit 0caf51abd8
2 changed files with 40 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

4
ChangeLog
View file

@ -1,3 +1,7 @@
2011-04-09 Alexandre Duret-Lutz <adl@lrde.epita.fr>
* HACKING: Add an example for using callgrind.
2011-04-06 Alexandre Duret-Lutz <adl@lrde.epita.fr> 2011-04-06 Alexandre Duret-Lutz <adl@lrde.epita.fr>
* iface/dve2/dve2check.cc (main): Catch out-of-memory errors * iface/dve2/dve2check.cc (main): Catch out-of-memory errors

40
HACKING
View file

@ -1,5 +1,5 @@
Bootstraping from GIT: Bootstraping from GIT
====================== =====================
Some files in SPOT's source tree are generated. They are distributed Some files in SPOT's source tree are generated. They are distributed
so that users do not need to tools to rebuild them, but we don't keep so that users do not need to tools to rebuild them, but we don't keep
@ -8,6 +8,8 @@ conflicts.
Here are the tools you need to bootstrap the GIT tree, or more Here are the tools you need to bootstrap the GIT tree, or more
generally if you plan to regenerate some of the generated files. generally if you plan to regenerate some of the generated files.
(None of these tools are required by end users installing a tarball
since the generated files they produce are distributed.)
GNU Autoconf >= 2.61 GNU Autoconf >= 2.61
GNU Automake >= 1.11 GNU Automake >= 1.11
@ -19,12 +21,12 @@ generally if you plan to regenerate some of the generated files.
Bootstrap the GIT tree by running Bootstrap the GIT tree by running
autoreconf -vfi % autoreconf -vfi
and then go on with the usual and then go on with the usual
./configure % ./configure
make % make
Tricks Tricks
@ -90,6 +92,23 @@ shorthand "libtool --mode=execute" as "libtool execute" or even
"libtool e". "libtool e".
Profiling with callgrind
------------------------
Install valgrind and kcachegrind.
Then run the command you want to profile through valgrind's callgrind
tool. For instance:
% libtool e valgrind --tool=callgrind ltl2tgba -f 'GFa & GFb'
This will output a file called 'callgrind.PID' where PID is the
process ID printed during valgrind's run. Load this file with
kcachegrind to get a graphical summary.
% kcachegrind ./callgrind.PID
Running coverage tests Running coverage tests
---------------------- ----------------------
@ -121,11 +140,12 @@ This is currently (April 2011) tricky to setup, because the
toolchain is not mature enough. toolchain is not mature enough.
You need: You need:
1) a version of GCC with gold and pluing linker enabled. 1. a version of GCC (>= 4.5) with gold and pluing linker enabled.
2) a version of Libtool that knows how to deal with 2. a version of Libtool that knows how to deal with
-flto flags (Libtool 2.4 will not work -- currently only -flto flags (Libtool 2.4 will not work -- currently only
the development version does.) the development version does.)
3) use static libraries instead of shared libraries. 3. to use static libraries instead of shared libraries
so that you get inter-libraries optimizations.
Here are example options to pass to configure: Here are example options to pass to configure:
@ -142,8 +162,8 @@ compiler error), while most others (like randtgba, dve2check, randltl,
...) do fine. ...) do fine.
Coding conventions: Coding conventions
=================== ==================
Here are the conventions we follow in Spot, so that the code looks Here are the conventions we follow in Spot, so that the code looks
homogeneous. Please follow these strictly. Since this is free homogeneous. Please follow these strictly. Since this is free