Author: njn Date: 2007-10-19 00:14:48 +0100 (Fri, 19 Oct 2007) New Revision: 7025
Log: Suggest compiling with --Wall. Modified: trunk/docs/xml/manual-core.xml Modified: trunk/docs/xml/manual-core.xml =================================================================== --- trunk/docs/xml/manual-core.xml 2007-10-18 23:02:29 UTC (rev 7024) +++ trunk/docs/xml/manual-core.xml 2007-10-18 23:14:48 UTC (rev 7025) @@ -116,8 +116,12 @@ this often makes things unmanagably slow, a reasonable compromise is to use <computeroutput>-O</computeroutput>. 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.</para> +chances of false positives or false negatives from Memcheck. Also, you +should compile your code with <computeroutput>-Wall</computeroutput> because +it can identify some or all of the problems that Valgrind can miss at the +higher optimisations levels. (Using <computeroutput>-Wall</computeroutput> +is also a good idea in general.) All other tools (as far as we know) are +unaffected by optimisation level.</para> <para>Valgrind understands both the older "stabs" debugging format, used by gcc versions prior to 3.1, and the newer DWARF2 and DWARF3 formats ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Valgrind-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-developers
