This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Document STDC_0_IN_SYSTEM_HEADERS
- To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Subject: Document STDC_0_IN_SYSTEM_HEADERS
- From: Neil Booth <neil at daikokuya dot demon dot co dot uk>
- Date: Sat, 16 Jun 2001 12:13:50 +0100
- Cc: martin at loewis dot home dot cs dot tu-berlin dot de, mengel at fnal dot gov,gcc-gnats at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
Joseph S. Myers wrote:-
> The target macro STDC_0_IN_SYSTEM_HEADERS is still undocumented; it should
> be documented in tm.texi.
OK to commit the following patch?
Neil.
* tm.texi: Document STDC_0_IN_SYSTEM_HEADERS.
Index: tm.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/tm.texi,v
retrieving revision 1.4
diff -u -p -r1.4 tm.texi
--- tm.texi 2001/06/14 22:51:18 1.4
+++ tm.texi 2001/06/16 11:10:55
@@ -8080,6 +8080,18 @@ The default definition of this macro is
arguments that the function accepts. Some people think a larger
threshold should be used on RISC machines.
+@findex STDC_0_IN_SYSTEM_HEADERS
+@item STDC_0_IN_SYSTEM_HEADERS
+In normal operation, the preprocessor expands @code{__STDC__} to the
+constant 1, to signify that GCC conforms to ISO Standard C@. On some
+hosts, like Solaris, the system compiler uses a different convention,
+where @code{__STDC__} is normally 0, but is 1 if the user specifies
+strict conformance to the C Standard.
+
+Defining @code{STDC_0_IN_SYSTEM_HEADERS} makes GNU CPP follows the host
+convention when processing system header files, but when processing user
+files @code{__STDC__} will always expand to 1.
+
@findex SCCS_DIRECTIVE
@item SCCS_DIRECTIVE
Define this if the preprocessor should ignore @code{#sccs} directives