From: Jakub Jelinek <jakub@redhat.com>
To: "Stubbs, Andrew" <Andrew_Stubbs@mentor.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: OpenMP auto-simd
Date: Wed, 2 Mar 2022 16:24:46 +0100 [thread overview]
Message-ID: <Yh+MPhzJq4h3UyYN@tucnak> (raw)
In-Reply-To: <2213264c2c5c467fb491f71051173873@svr-ies-mbx-01.mgc.mentorg.com>
On Wed, Mar 02, 2022 at 03:12:30PM +0000, Stubbs, Andrew wrote:
> Has anyone ever considered having GCC add the "simd" clause to offload (or regular) loop nests automatically?
>
> For example, something like "-fomp-auto-simd" would transform "distribute parallel" to "distribute parallel simd" automatically. Loop nests that already contain "simd" clauses or directives would remain unchanged, most likely.
I'm afraid we can't do that, at least not always. The simd has various
restrictions on what can appear inside of the body, etc. and we shouldn't
reject valid code just because we decided to add simd automatically (even if
the user asked for those through an option).
So, it could be done only if we would do analysis that it is safe to do
that.
Jakub
next prev parent reply other threads:[~2022-03-02 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 15:12 Stubbs, Andrew
2022-03-02 15:24 ` Jakub Jelinek [this message]
2022-03-02 16:11 ` Stubbs, Andrew
2022-03-08 14:29 ` Thomas Schwinge
2022-03-08 16:47 ` Stubbs, Andrew
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=Yh+MPhzJq4h3UyYN@tucnak \
--to=jakub@redhat.com \
--cc=Andrew_Stubbs@mentor.com \
--cc=gcc@gcc.gnu.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).