From: "Stubbs, Andrew" <Andrew_Stubbs@mentor.com>
To: "Schwinge, Thomas" <Thomas_Schwinge@mentor.com>,
Jakub Jelinek <jakub@redhat.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>, Tom de Vries <tdevries@suse.de>
Subject: RE: OpenMP auto-simd
Date: Tue, 8 Mar 2022 16:47:10 +0000 [thread overview]
Message-ID: <1bb165af072946b391160f69ff23ab7c@svr-ies-mbx-01.mgc.mentorg.com> (raw)
In-Reply-To: <8735jssejm.fsf@euler.schwinge.homeip.net>
> > I'm of the opinion that GCC is the one implementing OpenMP as intended
>
> I'm curious: how does one arrive at this conclusion?
Basically, any implementation for which a (significant) directive becomes a no-op is either a) not implementing the feature as intended, or b) is implementing it for a device configured differently to the one that inspired the directive. Since I'm pretty sure that (b) is not the case I settled my opinion on (a).
Now, it may be that the original intention is flawed and the deviant implementation is superior, but that's another matter.
Andrew
prev parent reply other threads:[~2022-03-08 16:47 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
2022-03-02 16:11 ` Stubbs, Andrew
2022-03-08 14:29 ` Thomas Schwinge
2022-03-08 16:47 ` Stubbs, Andrew [this message]
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=1bb165af072946b391160f69ff23ab7c@svr-ies-mbx-01.mgc.mentorg.com \
--to=andrew_stubbs@mentor.com \
--cc=Thomas_Schwinge@mentor.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=tdevries@suse.de \
/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).