The header files declaring interfaces to the operating system and
runtime libraries often cannot be written in strictly conforming C.
Therefore, GCC gives code found in system headers special
treatment. All warnings, other than those generated by ‘
(see Diagnostics), are suppressed while GCC is processing a system
header. Macros defined in a system header are immune to a few warnings
wherever they are expanded. This immunity is granted on an ad-hoc
basis, when we find that a warning generates lots of false positives
because of code in macros defined in system headers.
Normally, only the headers found in specific directories are considered system headers. These directories are determined when GCC is compiled. There are, however, two ways to make normal headers into system headers:
-idiraftercommand-line options are treated as system headers for the purposes of diagnostics.
#pragma GCC system_header, which tells GCC to consider the rest of the current include file a system header, no matter where it was found. Code that comes before the ‘
#pragma’ in the file is not affected.
#pragma GCC system_headerhas no effect in the primary source file.
On some targets, such as RS/6000 AIX, GCC implicitly surrounds all
system headers with an ‘
extern "C"’ block when compiling as C++.