From: Steve Ellcey <sellcey@cavium.com>
To: "james.greenhalgh" <james.greenhalgh@arm.com>,
"Sekhar, Ashwin" <Ashwin.Sekhar@cavium.com>,
gcc <gcc@gcc.gnu.org>,
"richard.earnshaw" <richard.earnshaw@arm.com>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>, nd <nd@arm.com>
Subject: Re: [Aarch64] Vector Function Application Binary Interface Specification for OpenMP
Date: Fri, 09 Feb 2018 21:47:00 -0000 [thread overview]
Message-ID: <1518212868.14236.47.camel@cavium.com> (raw)
James,
This is a follow-up to https://gcc.gnu.org/ml/gcc/2017-03/msg00109.html
 where you said:
| Hi Ashwin,
|Â
| Thanks for the question. ARM has defined a vector function ABI, based
| on the Vector Function ABI Specification you linked below, which
| is designed to be suitable for both the Advanced SIMD and Scalable
| Vector Extensions. There has not yet been a release of this document
| which I can point you at, nor can I give you an estimate of when the
| document will be published.
I was wondering if the function vector ABI has been published yet and
if so, where I could find it.
Steve Ellcey
sellcey@cavium.com
next reply other threads:[~2018-02-09 21:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 21:47 Steve Ellcey [this message]
2018-05-15 18:29 ` Francesco Petrogalli
2018-05-16 16:21 ` Steve Ellcey
2018-05-16 16:30 ` Richard Earnshaw (lists)
2018-05-16 17:30 ` Steve Ellcey
2018-05-16 21:11 ` Richard Sandiford
2018-05-24 17:50 ` Steve Ellcey
2018-05-26 10:09 ` Richard Sandiford
2018-05-26 22:13 ` Segher Boessenkool
2018-05-27 15:59 ` Jeff Law
2018-05-29 10:06 ` Richard Sandiford
2018-05-31 10:39 ` Alan Hayward
2018-06-12 3:11 ` Jeff Law
2018-06-11 23:06 ` Jeff Law
2018-07-02 18:16 ` Francesco Petrogalli
-- strict thread matches above, loose matches on Subject: below --
2017-03-15 9:50 Sekhar, Ashwin
2017-03-17 14:02 ` James Greenhalgh
2017-03-20 4:30 ` Sekhar, Ashwin
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=1518212868.14236.47.camel@cavium.com \
--to=sellcey@cavium.com \
--cc=Ashwin.Sekhar@cavium.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=gcc@gcc.gnu.org \
--cc=james.greenhalgh@arm.com \
--cc=nd@arm.com \
--cc=richard.earnshaw@arm.com \
/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).