From: Bill Schmidt <wschmidt@linux.vnet.ibm.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Segher Boessenkool <segher@kernel.crashing.org>
Subject: [PATCH, rs6000] Document location of ELF V2 ABI specification
Date: Wed, 29 Mar 2017 21:32:00 -0000 [thread overview]
Message-ID: <77c9a580-4ce4-5b21-7916-076696f5199a@linux.vnet.ibm.com> (raw)
Hi,
There is finally a permanent link to the OpenPOWER ELF V2 ABI Specification
document. This patch adds a paragraph to the PowerPC Built-Ins section of
the GCC documentation to describe its value and provide a link to it.
I've generated and verified the PDF, and it looks ok. I am very open to
changes in wording. Is this ok for trunk?
Thanks,
Bill
2017-03-29 Bill Schmidt <wschmidt@linux.vnet.ibm.com>
* doc/extend.texi (6.60.22 PowerPC AltiVec Built-in Functions):
Add reference to the OpenPOWER 64-Bit ELF V2 ABI Specification.
Index: gcc/doc/extend.texi
===================================================================
--- gcc/doc/extend.texi (revision 246566)
+++ gcc/doc/extend.texi (working copy)
@@ -15539,6 +15539,15 @@ Internally, GCC uses built-in functions to achieve
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
next reply other threads:[~2017-03-29 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 21:32 Bill Schmidt [this message]
2017-03-29 23:07 ` Segher Boessenkool
2017-03-31 15:07 ` Bill Schmidt
2017-04-01 17:15 ` Gerald Pfeifer
2017-04-04 15:16 ` Bill Schmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=77c9a580-4ce4-5b21-7916-076696f5199a@linux.vnet.ibm.com \
--to=wschmidt@linux.vnet.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).