System-Headers.html 4.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103
  1. <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
  2. <html>
  3. <!-- Copyright (C) 1987-2023 Free Software Foundation, Inc.
  4. Permission is granted to copy, distribute and/or modify this document
  5. under the terms of the GNU Free Documentation License, Version 1.3 or
  6. any later version published by the Free Software Foundation. A copy of
  7. the license is included in the
  8. section entitled "GNU Free Documentation License".
  9. This manual contains no Invariant Sections. The Front-Cover Texts are
  10. (a) (see below), and the Back-Cover Texts are (b) (see below).
  11. (a) The FSF's Front-Cover Text is:
  12. A GNU Manual
  13. (b) The FSF's Back-Cover Text is:
  14. You have freedom to copy and modify this GNU Manual, like GNU
  15. software. Copies published by the Free Software Foundation raise
  16. funds for GNU development. -->
  17. <!-- Created by GNU Texinfo 6.7, http://www.gnu.org/software/texinfo/ -->
  18. <head>
  19. <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  20. <title>System Headers (The C Preprocessor)</title>
  21. <meta name="description" content="System Headers (The C Preprocessor)">
  22. <meta name="keywords" content="System Headers (The C Preprocessor)">
  23. <meta name="resource-type" content="document">
  24. <meta name="distribution" content="global">
  25. <meta name="Generator" content="makeinfo">
  26. <link href="index.html" rel="start" title="Top">
  27. <link href="Index-of-Directives.html" rel="index" title="Index of Directives">
  28. <link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
  29. <link href="Header-Files.html" rel="up" title="Header Files">
  30. <link href="Macros.html" rel="next" title="Macros">
  31. <link href="Wrapper-Headers.html" rel="prev" title="Wrapper Headers">
  32. <style type="text/css">
  33. <!--
  34. a.summary-letter {text-decoration: none}
  35. blockquote.indentedblock {margin-right: 0em}
  36. div.display {margin-left: 3.2em}
  37. div.example {margin-left: 3.2em}
  38. div.lisp {margin-left: 3.2em}
  39. kbd {font-style: oblique}
  40. pre.display {font-family: inherit}
  41. pre.format {font-family: inherit}
  42. pre.menu-comment {font-family: serif}
  43. pre.menu-preformatted {font-family: serif}
  44. span.nolinebreak {white-space: nowrap}
  45. span.roman {font-family: initial; font-weight: normal}
  46. span.sansserif {font-family: sans-serif; font-weight: normal}
  47. ul.no-bullet {list-style: none}
  48. -->
  49. </style>
  50. </head>
  51. <body lang="en">
  52. <span id="System-Headers"></span><div class="header">
  53. <p>
  54. Previous: <a href="Wrapper-Headers.html" accesskey="p" rel="prev">Wrapper Headers</a>, Up: <a href="Header-Files.html" accesskey="u" rel="up">Header Files</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Index-of-Directives.html" title="Index" rel="index">Index</a>]</p>
  55. </div>
  56. <hr>
  57. <span id="System-Headers-1"></span><h3 class="section">2.8 System Headers</h3>
  58. <span id="index-system-header-files-1"></span>
  59. <p>The header files declaring interfaces to the operating system and
  60. runtime libraries often cannot be written in strictly conforming C.
  61. Therefore, GCC gives code found in <em>system headers</em> special
  62. treatment. All warnings, other than those generated by &lsquo;<samp>#warning</samp>&rsquo;
  63. (see <a href="Diagnostics.html">Diagnostics</a>), are suppressed while GCC is processing a system
  64. header. Macros defined in a system header are immune to a few warnings
  65. wherever they are expanded. This immunity is granted on an ad-hoc
  66. basis, when we find that a warning generates lots of false positives
  67. because of code in macros defined in system headers.
  68. </p>
  69. <p>Normally, only the headers found in specific directories are considered
  70. system headers. These directories are determined when GCC is compiled.
  71. There are, however, two ways to make normal headers into system headers:
  72. </p>
  73. <ul>
  74. <li> Header files found in directories added to the search path with the
  75. <samp>-isystem</samp> and <samp>-idirafter</samp> command-line options are
  76. treated as system headers for the purposes of diagnostics.
  77. </li><li> <span id="index-_0023pragma-GCC-system_005fheader"></span>
  78. There is also a directive, <code>#pragma&nbsp;GCC&nbsp;<span class="nolinebreak">system_header</span><!-- /@w --></code>, which
  79. tells GCC to consider the rest of the current include file a system
  80. header, no matter where it was found. Code that comes before the
  81. &lsquo;<samp>#pragma</samp>&rsquo; in the file is not affected. <code>#pragma&nbsp;GCC&nbsp;<span class="nolinebreak">system_header</span><!-- /@w --></code> has no effect in the primary source file.
  82. </li></ul>
  83. <p>On some targets, such as RS/6000 AIX, GCC implicitly surrounds all
  84. system headers with an &lsquo;<samp>extern &quot;C&quot;</samp>&rsquo; block when compiling as C++.
  85. </p>
  86. </body>
  87. </html>