Understanding compiler warning options
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: gcc-help@xxxxxxxxxxx
- Subject: Understanding compiler warning options
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- Date: Tue, 29 Sep 2015 19:41:23 -0400
- Authentication-results: sourceware.org; auth=none
- User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
I am trying to understand how the compiler decides which warnings are
issued when compiling a translation unit.
What is the default warnings that are issued if no compiler warning
options is set on the command line ?
If I set a general option, such as -w, -Wall, or -Wextra, do these get
overridden by more specific compiler options no matter where in the
command line they are encountered, or does the order of the compiler
warnings on the command line matter in such a case ? As a specific
practical example if the command line has "-Wno-unused-local-typedef
-Wall ..." does the "-Wno-unused-local-typedef" override the "-Wall"
option ?
[Index of Archives]
[Linux C Programming]
[Linux Kernel]
[eCos]
[Fedora Development]
[Fedora Announce]
[Autoconf]
[The DWARVES Debugging Tools]
[Yosemite Campsites]
[Yosemite News]
[Linux GCC]