From: Kirill Yukhin <kirill.yukhin@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Joseph Myers <joseph@codesourcery.com>, Jeff Law <law@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, VECTOR ABI] Add __attribute__((__simd__)) to GCC.
Date: Thu, 15 Oct 2015 14:48:00 -0000 [thread overview]
Message-ID: <20151015144739.GB2191@msticlxl57.ims.intel.com> (raw)
In-Reply-To: <20151015143909.GF478@tucnak.redhat.com>
Hi Jakub,
On 15 Oct 16:39, Jakub Jelinek wrote:
> On Thu, Oct 15, 2015 at 05:33:32PM +0300, Kirill Yukhin wrote:
> > --- a/gcc/doc/extend.texi
> > +++ b/gcc/doc/extend.texi
> > @@ -3066,6 +3066,20 @@ This function attribute make a stack protection of the function if
> > flags @option{fstack-protector} or @option{fstack-protector-strong}
> > or @option{fstack-protector-explicit} are set.
> >
> > +@item simd
> > +@cindex @code{simd} function attribute.
> > +This attribute enables creation of one or more function versions that
> > +can process multiple arguments using SIMD instructions from a
> > +single invocation. Specifying this attribute allows compiler to
> > +assume that such a versions are available at link time (provided
> > +in the same or another translation unit). Generated versions are
> > +target dependent and described in corresponding Vector ABI document. For
> > +x86_64 target this document can be found
> > +@w{@uref{https://sourceware.org/glibc/wiki/libmvec?action=AttachFile&do=view&target=VectorABI.txt,here}}.
> > +It is prohibited to use the attribute along with Cilk Plus's @code{vector}
> > +attribute. If the attribute is specified and @code{#pragma omp declare simd}
> > +presented on a declaration, then the attribute is ignored.
>
> Is that what is implemented? I mean, isn't the argument ignored only
> if #pragma omp declare simd is present and -fopenmp or -fopenmp-simd
> passed on the command line, because otherwise the pragma is ignored?
You're right. The attribute is ignored if `pragma omp declare simd' is
got in charge. Which happens only if -fopenmp or -fopenmp-simd is
are passed.
Updated hunk for doc/extend.texi is in the bottom.
>
> Jakub
--
Thanks, K
$ git show
commit ffda5e84f2b79a28f4104b1eda2df0f907821ec0
Author: Kirill Yukhin <kirill.yukhin@intel.com>
Date: Thu Oct 15 17:10:53 2015 +0300
[vector-attr] Add documentation.
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 79440d3..d9463d8 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -3066,6 +3066,21 @@ This function attribute make a stack protection of the function if
flags @option{fstack-protector} or @option{fstack-protector-strong}
or @option{fstack-protector-explicit} are set.
+@item simd
+@cindex @code{simd} function attribute.
+This attribute enables creation of one or more function versions that
+can process multiple arguments using SIMD instructions from a
+single invocation. Specifying this attribute allows compiler to
+assume that such a versions are available at link time (provided
+in the same or another translation unit). Generated versions are
+target dependent and described in corresponding Vector ABI document. For
+x86_64 target this document can be found
+@w{@uref{https://sourceware.org/glibc/wiki/libmvec?action=AttachFile&do=view&target=VectorABI.txt,here}}.
+It is prohibited to use the attribute along with Cilk Plus's @code{vector}
+attribute. If the attribute is specified and @code{#pragma omp declare simd}
+presented on a declaration and @code{-fopenmp} or @code{-fopenmp-simd}
+switch is specified, then the attribute is ignored.
+
@item target (@var{options})
@cindex @code{target} function attribute
Multiple target back ends implement the @code{target} attribute
next prev parent reply other threads:[~2015-10-15 14:48 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
2015-10-15 14:34 ` Kirill Yukhin
2015-10-15 14:39 ` Jakub Jelinek
2015-10-15 14:48 ` Kirill Yukhin [this message]
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=20151015144739.GB2191@msticlxl57.ims.intel.com \
--to=kirill.yukhin@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.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).