From: rth <rth@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Sat, 2 Oct 1999 18:16:33 +0000 (+0000)
Subject: Jim Kingdon  <http://developer.redhat.com>
X-Git-Url: http://git.sourceforge.jp/view?a=commitdiff_plain;h=545c060b5b382c46e21433120bc48331888e5376;p=pf3gnuchains%2Fgcc-fork.git

Jim Kingdon  <http://developer.redhat.com>

        * extend.texi: Grammar fix in __extension__ text.


git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@29773 138bc75d-0d04-0410-961f-82ee72b054a4
---

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 9af40180f9e..a9319fa8a24 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+Sat Oct  2 11:16:00 1999  Jim Kingdon  <http://developer.redhat.com>
+
+	* extend.texi: Grammar fix in __extension__ text.
+
 Sat Oct  2 11:06:31 1999  Richard Henderson  <rth@cygnus.com>
 
 	* md.texi (define_peephole2): New section.
diff --git a/gcc/extend.texi b/gcc/extend.texi
index e98e63e7988..b151b6b5c6e 100644
--- a/gcc/extend.texi
+++ b/gcc/extend.texi
@@ -2973,7 +2973,7 @@ macros to replace them with the customary keywords.  It looks like this:
 @end example
 
 @findex __extension__
-@samp{-pedantic} and other options causes warnings for many GNU C extensions.
+@samp{-pedantic} and other options cause 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