From ee773fcc770aa8210e81cd94916f3ecb50c51458 Mon Sep 17 00:00:00 2001 From: Neil Booth Date: Sun, 17 Jun 2001 09:50:00 +0000 Subject: [PATCH] * tm.texi: Document STDC_0_IN_SYSTEM_HEADERS. From-SVN: r43426 --- gcc/ChangeLog | 4 ++++ gcc/doc/tm.texi | 12 ++++++++++++ 2 files changed, 16 insertions(+) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index e0092a4900b..c6426bf0bd8 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,7 @@ +2001-06-17 Neil Booth + + * tm.texi: Document STDC_0_IN_SYSTEM_HEADERS. + Sat Jun 16 20:20:39 2001 Richard Kenner * expr.c (expand_expr, case ADDR_EXPR): If taking address of SAVE_EXPR, diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi index 2e430aec2ad..5359f7a9d44 100644 --- a/gcc/doc/tm.texi +++ b/gcc/doc/tm.texi @@ -8080,6 +8080,18 @@ The default definition of this macro is 64 plus 8 times the number of 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 -- 2.30.2