From: Joseph Myers <joseph@codesourcery.com>
To: Kirill Yukhin <kirill.yukhin@gmail.com>
Cc: Jeff Law <law@redhat.com>, Jakub Jelinek <jakub@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, VECTOR ABI] Add __attribute__((__simd__)) to GCC.
Date: Wed, 14 Oct 2015 13:40:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1510141335490.15356@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20151014123601.GA38813@msticlxl57.ims.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1606 bytes --]
On Wed, 14 Oct 2015, Kirill Yukhin wrote:
> Is it ok for trunk?
This patch has no documentation. Documentation for new attributes must be
added to extend.texi.
> Enables creation of one or more versions that can process multiple
> arguments using SIMD instructions from a single invocation from a SIMD
> loop. It is ultimately an alias to `omp declare simdâ pragma, available
> w/o additional compiler switches. It is prohibited to use the attribute
> along with Cilk Plusâs `vectorâ attribute. If the attribute is specified
> and `pragma omp declare simdâ presents on a decl, then the attribute is
> ignored.
This is missing the key information that it's not just about *creation* of
the versions, it's about (in the case of an external declaration)
*assuming* such versions were created in another translation unit. And
you should have a link to the external ABI documents specifying for each
architecture for which this involves such an assumption exactly what
versions may be assumed to be present - this is what's required to be able
to use the attribute in headers for a library and know that future GCC
versions won't reinterpret the attribute as implying some versions for
future ISA extensions are also present.
I wonder whether the syntax for this attribute should allow optional
arguments to describe what versions are present, but maybe that can be
deferred until e.g. you want a way in future for a library to specify it
has an AVX1024 version of a function as well as the baseline ABI set of
versions.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2015-10-14 13:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151005130733.GB62312@msticlxl57.ims.intel.com>
[not found] ` <alpine.DEB.2.10.1510051320120.16355@digraph.polyomino.org.uk>
[not found] ` <561551B0.70507@redhat.com>
2015-10-14 12:36 ` Kirill Yukhin
2015-10-14 13:40 ` Joseph Myers [this message]
2015-10-15 14:34 ` Kirill Yukhin
2015-10-15 14:39 ` Jakub Jelinek
2015-10-15 14:48 ` Kirill Yukhin
2015-10-22 12:25 ` Kirill Yukhin
2015-10-22 12:50 ` Joseph Myers
2015-10-23 14:16 ` Kirill Yukhin
2015-10-23 14:23 ` Joseph Myers
2015-10-27 14:09 ` Kirill Yukhin
2015-10-27 14:17 ` Jakub Jelinek
2015-10-28 9:40 ` Kirill Yukhin
2015-10-29 8:56 ` Jakub Jelinek
2015-11-10 8:44 ` Kirill Yukhin
2015-11-10 8:58 ` Jakub Jelinek
2015-11-13 11:55 ` Kirill Yukhin
2015-11-13 12:16 ` Jakub Jelinek
2015-12-02 12:47 ` Kirill Yukhin
2015-12-02 17:40 ` Jeff Law
2015-12-02 17:42 ` Jakub Jelinek
2015-11-18 9:39 ` Andreas Schwab
2015-11-18 9:46 ` Andreas Schwab
2015-11-18 14:11 ` Kirill Yukhin
2015-11-18 17:01 ` Jeff Law
2015-11-20 12:15 ` Kyrill Tkachov
2015-11-20 13:33 ` Kirill Yukhin
2015-11-20 19:48 ` Jeff Law
2015-11-17 16:10 David Edelsohn
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=alpine.DEB.2.10.1510141335490.15356@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=kirill.yukhin@gmail.com \
--cc=law@redhat.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).