From 3a44da9ea761716a91f8524e901a7d42d4a3f96c Mon Sep 17 00:00:00 2001 From: Bill Schmidt Date: Fri, 31 Mar 2017 15:04:34 +0000 Subject: [PATCH] extend.texi (PowerPC AltiVec Built-in Functions): Add reference to the OpenPOWER 64-Bit ELF V2 ABI Specification. 2017-03-31 Bill Schmidt * doc/extend.texi (PowerPC AltiVec Built-in Functions): Add reference to the OpenPOWER 64-Bit ELF V2 ABI Specification. From-SVN: r246617 --- gcc/ChangeLog | 5 +++++ gcc/doc/extend.texi | 9 +++++++++ 2 files changed, 14 insertions(+) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 594b32a4563..3fd3b841698 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,8 @@ +2017-03-31 Bill Schmidt + + * doc/extend.texi (PowerPC AltiVec Built-in Functions): Add + reference to the OpenPOWER 64-Bit ELF V2 ABI Specification. + 2017-03-31 Matthew Fortune * config/mips/mips-msa.md (msa_vec_extract_): Update diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index fadbc9673f0..0f44ece7720 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 -- 2.30.2