This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[DOC PATCH] extend.texi AltiVec builtin fixes
- From: Janis Johnson <janis187 at us dot ibm dot com>
- To: gcc-patches at gcc dot gnu dot org
- Date: Thu, 12 Aug 2004 14:42:14 -0700
- Subject: [DOC PATCH] extend.texi AltiVec builtin fixes
Document some more differences between GCC's AltiVec programming
interface and that described in the PIM and fix an incorrect statement.
Tested with 'make info' and 'make dvi'. OK for mainline?
I'm backporting several AltiVec fixes for 3.4-branch and will include
all documentation updates in that patch set.
2004-08-12 Janis Johnson <janis187@us.ibm.com>
* doc/extend.texi (AltiVec builtins): Document additional differences
from the Motorola AltiVec PIM.
Index: doc/extend.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/extend.texi,v
retrieving revision 1.207
diff -u -p -r1.207 extend.texi
--- doc/extend.texi 12 Aug 2004 21:19:08 -0000 1.207
+++ doc/extend.texi 12 Aug 2004 21:37:13 -0000
@@ -5769,7 +5769,18 @@ same type as the variable it is initiali
@item
If @code{signed} or @code{unsigned} is omitted, the vector type defaults
-to @code{signed}.
+to @code{signed} for @code{vector int} or @code{vector short} and to
+@code{unsigned} for @code{vector char}.
+
+@item
+Compiling with @option{-maltivec} adds keywords @code{__vector},
+@code{__pixel}, and @code{__bool}. Macros @option{vector},
+@code{pixel}, and @code{bool} are defined in @code{<altivec.h>} and can
+be undefined.
+
+@item
+GCC allows using a @code{typedef} name as the type specifier for a
+vector type.
@item
For C, overloaded functions are implemented with macros so the following