|
From: <sv...@va...> - 2005-06-18 15:08:08
|
Author: njn
Date: 2005-06-18 16:07:39 +0100 (Sat, 18 Jun 2005)
New Revision: 3935
Log:
Minor rearrangement, no functional change.
Modified:
trunk/include/valgrind.h
Modified: trunk/include/valgrind.h
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/include/valgrind.h 2005-06-18 11:58:18 UTC (rev 3934)
+++ trunk/include/valgrind.h 2005-06-18 15:07:39 UTC (rev 3935)
@@ -55,6 +55,20 @@
*/
=20
=20
+/* This file is for inclusion into client (your!) code.
+
+ You can use these macros to manipulate and query Valgrind's=20
+ execution inside your own programs.
+
+ The resulting executables will still run without Valgrind, just a
+ little bit more slowly than they otherwise would, but otherwise
+ unchanged. When not running on valgrind, each client request
+ consumes very few (eg. < 10) instructions, so the resulting performan=
ce
+ 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. */
+
#ifndef __VALGRIND_H
#define __VALGRIND_H
=20
@@ -70,21 +84,10 @@
# endif /* NVALGRIND */
#endif
=20
+/* ------------------------------------------------------------------ */
+/* The architecture-specific part */
+/* ------------------------------------------------------------------ */
=20
-/* This file is for inclusion into client (your!) code.
-
- You can use these macros to manipulate and query Valgrind's=20
- execution inside your own programs.
-
- The resulting executables will still run without Valgrind, just a
- little bit more slowly than they otherwise would, but otherwise
- unchanged. When not running on valgrind, each client request
- consumes very few (eg. < 10) instructions, so the resulting performan=
ce
- 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. */
-
#ifdef NVALGRIND
=20
/* Define NVALGRIND to completely remove the Valgrind magic sequence
@@ -187,6 +190,10 @@
#endif /* NVALGRIND */
=20
=20
+/* ------------------------------------------------------------------ */
+/* The architecture-independent part */
+/* ------------------------------------------------------------------ */
+
/* Some request codes. There are many more of these, but most are not
exposed to end-user view. These are the public ones, all of the
form 0x1000 + small_number.
@@ -231,7 +238,7 @@
VG_USERREQ__MEMPOOL_FREE =3D 0x1306,
=20
/* Allow printfs to valgrind log. */
- VG_USERREQ__PRINTF =3D 0x1401,
+ VG_USERREQ__PRINTF =3D 0x1401,
VG_USERREQ__PRINTF_BACKTRACE =3D 0x1402,
=20
/* Stack support. */
|