Differences between version 7 and previous revision of -Wall.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
Newer page: | version 7 | Last edited on Friday, October 31, 2003 10:21:51 am | by StuartYeates | Revert |
Older page: | version 6 | Last edited on Sunday, August 24, 2003 8:23:19 am | by AristotlePagaltzis | Revert |
@@ -1,9 +1,9 @@
When running [gcc(1)], [-Wall] is the [CommandLine] option that enables all warnings. Generally the first thing people will look for when debugging or helping others with [C]/[C++] code is that it compiles with [-Wall].
-[-Wall] warns about a great many things which are normally harmless in normal circumstances but can be dangerous at others. __-pedantic__ warns against things that are technically wrong but cannot lead to problems for [gcc(1)] and __-pedantic-errors__ issues errors for such quibbles. __-pedantic__ and __-pedantic-errors__ are not usually used unless the code is being written with the intention of porting it to exotic hardware.
+[-Wall] warns about a great many things which are normally harmless in normal circumstances but can be dangerous at others. __-pedantic__ also
warns against things that are technically wrong but cannot lead to problems for [gcc(1)] and __-pedantic-errors__ issues errors for such quibbles. __-pedantic__ and __-pedantic-errors__ are not usually used unless the code is being written with the intention of porting it to exotic hardware, as a last ditch attempt to find an illusive bug or as a method of evaluating the quality of code (StuartYeates always uses these flags when marking [C]/[C++] assignments)
.
-It is often a good idea to add [-Wall] to your __CFLAGS__ environment variable. The second thing to do after adding [-Wall] is to add __-g__ so you can get debugging symbols when your program crashes.
+It is often a good idea to add [-Wall] to your __CFLAGS__ environment variable. The second thing to do after adding [-Wall] is to add __-g__ so you can get debugging symbols when your program crashes. Unlike [-Wall], __-g__ can effect the RunTime performance of the generated programs so is not recommended when building core system components on a production system
.
Many programmers have a line similar to
export CFLAGS="-Wall -g"
in their __.profile__.