From: Julian Seward Date: Sat, 15 Mar 2003 23:39:11 +0000 (+0000) Subject: Comment change only: remove discussion of --client-perms flag and clarify X-Git-Tag: svn/VALGRIND_2_0_0~268 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=d3da5cf2bd3e142550202a4906eb7d46e704f466;p=thirdparty%2Fvalgrind.git Comment change only: remove discussion of --client-perms flag and clarify performance consequences of client requests. MERGE TO STABLE git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1460 --- diff --git a/include/valgrind.h b/include/valgrind.h index c5cf5ab329..b81961b864 100644 --- a/include/valgrind.h +++ b/include/valgrind.h @@ -78,12 +78,12 @@ The resulting executables will still run without Valgrind, just a little bit more slowly than they otherwise would, but otherwise - unchanged. - - When run on Valgrind with --client-perms=yes, Valgrind observes - these macro calls and takes appropriate action. When run on - Valgrind with --client-perms=no (the default), Valgrind observes - these macro calls but does not take any action as a result. */ + unchanged. When not running on valgrind, each client request + consumes about 9 x86 instructions, so the resulting performance + loss is negligible unless you plan to execute client requests + millions of times per second. Nevertheless, if that is still a + problem, you can compile with the NVALGRIND symbol defined (gcc + -DNVALGRIND) so that client requests are not even compiled in. */