Commit 63d0dca4 by David Edelsohn Committed by David Edelsohn

re PR target/27544 (attribute altivec is not documented)

        PR target/27544
        * doc/extend.texi (PowerPC Variable Attributes): Mention altivec.
        (PowerPC Type Attributes): New.

From-SVN: r116478
parent ec6aa500
2006-08-26 David Edelsohn <edelsohn@gnu.org>
PR target/27544
* doc/extend.texi (PowerPC Variable Attributes): Mention altivec.
(PowerPC Type Attributes): New.
2006-08-26 Bob Wilson <bob.wilson@acm.org> 2006-08-26 Bob Wilson <bob.wilson@acm.org>
* config/xtensa/xtensa.c (function_arg_boundary): New. * config/xtensa/xtensa.c (function_arg_boundary): New.
......
...@@ -3374,11 +3374,14 @@ Here, @code{t5} will take up 2 bytes. ...@@ -3374,11 +3374,14 @@ Here, @code{t5} will take up 2 bytes.
@subsection PowerPC Variable Attributes @subsection PowerPC Variable Attributes
Two attributes are currently defined for PowerPC configurations: Three attributes currently are defined for PowerPC configurations:
@code{ms_struct} and @code{gcc_struct}. @code{altivec}, @code{ms_struct} and @code{gcc_struct}.
For full documentation of these attributes please see the documentation For full documentation of the struct attributes please see the
in the @xref{i386 Variable Attributes}, section. documentation in the @xref{i386 Variable Attributes}, section.
For documentation of @code{altivec} attribute please see the
documentation in the @xref{PowerPC Type Attributes}, section.
@subsection Xstormy16 Variable Attributes @subsection Xstormy16 Variable Attributes
...@@ -3674,7 +3677,6 @@ declaration, the above program would abort when compiled with ...@@ -3674,7 +3677,6 @@ declaration, the above program would abort when compiled with
above in recent GCC versions. above in recent GCC versions.
@item visibility @item visibility
In C++, attribute visibility (@pxref{Function Attributes}) can also be In C++, attribute visibility (@pxref{Function Attributes}) can also be
applied to class, struct, union and enum types. Unlike other type applied to class, struct, union and enum types. Unlike other type
attributes, the attribute must appear between the initial keyword and attributes, the attribute must appear between the initial keyword and
...@@ -3710,6 +3712,7 @@ virtual table for @code{C} is not exported. (You can use ...@@ -3710,6 +3712,7 @@ virtual table for @code{C} is not exported. (You can use
@code{__attribute__} instead of @code{__declspec} if you prefer, but @code{__attribute__} instead of @code{__declspec} if you prefer, but
most Symbian OS code uses @code{__declspec}.) most Symbian OS code uses @code{__declspec}.)
@anchor{i386 Type Attributes}
@subsection i386 Type Attributes @subsection i386 Type Attributes
Two attributes are currently defined for i386 configurations: Two attributes are currently defined for i386 configurations:
...@@ -3735,6 +3738,30 @@ To specify multiple attributes, separate them by commas within the ...@@ -3735,6 +3738,30 @@ To specify multiple attributes, separate them by commas within the
double parentheses: for example, @samp{__attribute__ ((aligned (16), double parentheses: for example, @samp{__attribute__ ((aligned (16),
packed))}. packed))}.
@anchor{PowerPC Type Attributes}
@subsection PowerPC Type Attributes
Three attributes currently are defined for PowerPC configurations:
@code{altivec}, @code{ms_struct} and @code{gcc_struct}.
For full documentation of the struct attributes please see the
documentation in the @xref{i386 Type Attributes}, section.
The @code{altivec} attribute allows one to declare AltiVec vector data
types supported by the AltiVec Programming Interface Manual. The
attribute requires an argument to specify one of three vector types:
@code{vector__}, @code{pixel__} (always followed by unsigned short),
and @code{bool__} (always followed by unsigned).
@smallexample
__attribute__((altivec(vector__)))
__attribute__((altivec(pixel__))) unsigned short
__attribute__((altivec(bool__))) unsigned
@end smallexample
These attributes mainly are intended to support the @code{__vector},
@code{__pixel}, and @code{__bool} AltiVec keywords.
@node Inline @node Inline
@section An Inline Function is As Fast As a Macro @section An Inline Function is As Fast As a Macro
@cindex inline functions @cindex inline functions
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment