diff options
| author | Bill Schmidt <wschmidt@linux.vnet.ibm.com> | 2017-03-31 15:04:34 +0000 |
|---|---|---|
| committer | William Schmidt <wschmidt@gcc.gnu.org> | 2017-03-31 15:04:34 +0000 |
| commit | 3a44da9ea761716a91f8524e901a7d42d4a3f96c (patch) | |
| tree | 9bfce9326265b1671ab61a01f1ef50878e949097 | |
| parent | f6a7a9d51c41b7795604edf48865f941c7db7cc8 (diff) | |
| download | gcc-3a44da9ea761716a91f8524e901a7d42d4a3f96c.zip gcc-3a44da9ea761716a91f8524e901a7d42d4a3f96c.tar.gz gcc-3a44da9ea761716a91f8524e901a7d42d4a3f96c.tar.bz2 | |
extend.texi (PowerPC AltiVec Built-in Functions): Add reference to the OpenPOWER 64-Bit ELF V2 ABI Specification.
2017-03-31 Bill Schmidt <wschmidt@linux.vnet.ibm.com>
* doc/extend.texi (PowerPC AltiVec Built-in Functions): Add
reference to the OpenPOWER 64-Bit ELF V2 ABI Specification.
From-SVN: r246617
| -rw-r--r-- | gcc/ChangeLog | 5 | ||||
| -rw-r--r-- | gcc/doc/extend.texi | 9 |
2 files changed, 14 insertions, 0 deletions
diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 594b32a..3fd3b84 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,8 @@ +2017-03-31 Bill Schmidt <wschmidt@linux.vnet.ibm.com> + + * doc/extend.texi (PowerPC AltiVec Built-in Functions): Add + reference to the OpenPOWER 64-Bit ELF V2 ABI Specification. + 2017-03-31 Matthew Fortune <matthew.fortune@imgtec.com> * config/mips/mips-msa.md (msa_vec_extract_<msafmt_f>): Update diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index fadbc96..0f44ece 100644 --- a/gcc/doc/extend.texi +++ b/gcc/doc/extend.texi @@ -15539,6 +15539,15 @@ Internally, GCC uses built-in functions to achieve the functionality in the aforementioned header file, but they are not supported and are subject to change without notice. +GCC complies with the OpenPOWER 64-Bit ELF V2 ABI Specification, +which may be found at +@uref{http://openpowerfoundation.org/wp-content/uploads/resources/leabi-prd/content/index.html}. +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. + The following interfaces are supported for the generic and specific AltiVec operations and the AltiVec predicates. In cases where there is a direct mapping between generic and specific operations, only the |