From: Jakub Jelinek <jakub@redhat.com>
To: "Grosse-Bley, Paul Leonard" <rz230@uni-heidelberg.de>
Cc: gcc@gcc.gnu.org
Subject: Re: GOMP: OMP 5.1: simd construct for non-pointer random access iterators
Date: Thu, 15 Dec 2022 21:40:45 +0100 [thread overview]
Message-ID: <Y5uGTUNhtv0ut/Ud@tucnak> (raw)
In-Reply-To: <3759c6-639b8400-1f1-4a5acd00@89943933>
On Thu, Dec 15, 2022 at 09:31:50PM +0100, Grosse-Bley, Paul Leonard wrote:
>
> Hi together,
>
> I just ran into the issue that `#pragma omp simd` does not work on C++ iterator loops (godbolt).
> >From going through the specifications I understand that this restriction was part of 4.5 and 5.0, but was dropped with 5.1.
> As I couldn't find this change in the table of 5.1 (or 5.2) features for libgomp, I wanted to ask if this is on the horizon.
That is not the case.
OpenMP 5.1 has the restriction on p. 137 l. 22:
"The only random access iterator types that are allowed for the associated loops are pointer
types."
OpenMP 5.2 has the same thing on p. 235 l. 31.
Even TR11 (first OpenMP 6.0 draft) has the same wording on p. 246 l. 2.
Jakub
next prev parent reply other threads:[~2022-12-15 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 20:31 Grosse-Bley, Paul Leonard
2022-12-15 20:40 ` Jakub Jelinek [this message]
2022-12-15 20:53 ` Tobias Burnus
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=Y5uGTUNhtv0ut/Ud@tucnak \
--to=jakub@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=rz230@uni-heidelberg.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).