From c7bef26e28a444f62a5bf4ed20647664a81142ec Mon Sep 17 00:00:00 2001 From: Nicholas Nethercote Date: Thu, 18 Oct 2007 23:14:48 +0000 Subject: [PATCH] Suggest compiling with --Wall. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7025 --- docs/xml/manual-core.xml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml index 6ff0c9bdb9..2e061ae2ae 100644 --- a/docs/xml/manual-core.xml +++ b/docs/xml/manual-core.xml @@ -116,8 +116,12 @@ tool. So the best solution is to turn off optimisation altogether. Since this often makes things unmanagably slow, a reasonable compromise is to use -O. This gets you the majority of the benefits of higher optimisation levels whilst keeping relatively small the -chances of false positives or false negatives from Memcheck. All other -tools (as far as we know) are unaffected by optimisation level. +chances of false positives or false negatives from Memcheck. Also, you +should compile your code with -Wall because +it can identify some or all of the problems that Valgrind can miss at the +higher optimisations levels. (Using -Wall +is also a good idea in general.) All other tools (as far as we know) are +unaffected by optimisation level. Valgrind understands both the older "stabs" debugging format, used by gcc versions prior to 3.1, and the newer DWARF2 and DWARF3 formats -- 2.47.2