diff options
| author | law <law@138bc75d-0d04-0410-961f-82ee72b054a4> | 1999-09-23 19:41:04 +0000 |
|---|---|---|
| committer | law <law@138bc75d-0d04-0410-961f-82ee72b054a4> | 1999-09-23 19:41:04 +0000 |
| commit | 6b88ddb7b4aeb06cbe7df6a797507190fda662f5 (patch) | |
| tree | 304f1a75c0a3ad3021946314abbaa0c4da7ba744 | |
| parent | d62f46048dc8057655482cb07ec238e73b05295a (diff) | |
| download | gcc-6b88ddb7b4aeb06cbe7df6a797507190fda662f5.tar.gz | |
Should have been checked in with Kingdon's change.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@29629 138bc75d-0d04-0410-961f-82ee72b054a4
| -rw-r--r-- | gcc/extend.texi | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/gcc/extend.texi b/gcc/extend.texi index 82e955993d8..e98e63e7988 100644 --- a/gcc/extend.texi +++ b/gcc/extend.texi @@ -2973,7 +2973,8 @@ macros to replace them with the customary keywords. It looks like this: @end example @findex __extension__ -@samp{-pedantic} causes warnings for many GNU C extensions. You can +@samp{-pedantic} and other options causes warnings for many GNU C extensions. +You can prevent such warnings within one expression by writing @code{__extension__} before the expression. @code{__extension__} has no effect aside from this. |