extend.texi (PowerPC AltiVec Built-in Functions): Grammar correction.
authorBill Schmidt <wschmidt@linux.vnet.ibm.com>
Tue, 4 Apr 2017 16:31:58 +0000 (16:31 +0000)
committerWilliam Schmidt <wschmidt@gcc.gnu.org>
Tue, 4 Apr 2017 16:31:58 +0000 (16:31 +0000)
2017-04-04  Bill Schmidt  <wschmidt@linux.vnet.ibm.com>

* doc/extend.texi (PowerPC AltiVec Built-in Functions): Grammar
correction.

From-SVN: r246684

gcc/ChangeLog
gcc/doc/extend.texi

index 4136a2922b904deae39b74f9d94e1f993f6376ec..d60dd0b91e171fec37f67576bc15c2302fb9a1fe 100644 (file)
@@ -1,3 +1,8 @@
+2017-04-04  Bill Schmidt  <wschmidt@linux.vnet.ibm.com>
+
+       * doc/extend.texi (PowerPC AltiVec Built-in Functions): Grammar
+       correction.
+
 2017-04-04  Thomas Preud'homme  <thomas.preudhomme@arm.com>
 
        PR target/80307
index 0f44ece7720d059211f9a313451ef2f06bb82e66..219fa2cf5bd881536717ebd7cd4181fa4fe9e96b 100644 (file)
@@ -15546,7 +15546,7 @@ Appendix A of this document lists the vector API interfaces that must be
 provided by compliant compilers.  Programmers should preferentially use
 the interfaces described therein.  However, historically GCC has provided
 additional interfaces for access to vector instructions.  These are
-described briefly below.
+briefly described below.
 
 The following interfaces are supported for the generic and specific
 AltiVec operations and the AltiVec predicates.  In cases where there