From: Tobias Burnus <tobias@codesourcery.com>
To: "Grosse-Bley, Paul Leonard" <rz230@uni-heidelberg.de>, <gcc@gcc.gnu.org>
Subject: Re: GOMP: OMP 5.1: simd construct for non-pointer random access iterators
Date: Thu, 15 Dec 2022 21:53:50 +0100 [thread overview]
Message-ID: <656ea043-b4aa-dad3-1806-3145320623c2@codesourcery.com> (raw)
In-Reply-To: <3759c6-639b8400-1f1-4a5acd00@89943933>
Hi,
On 15.12.22 21:31, Grosse-Bley, Paul Leonard wrote:
> 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.
I assume that it is about "non-pointer random access iterators" – as the
subject line states.
In OpenMP 5.0, there is:
"2.9.1 Canonical Loop Form": "In the simd construct the only random
access iterator types that are allowed for var are pointer types."
[OpenMP 5.0, 100:15-16]
But I still see in OpenMP 5.1:
"2.11.5.1 simd Construct": "Restrictions to the simd construct are as
follows: ... [C++] The only random access iterator types that are
allowed for the associated loops are pointer types." [OpenMP 5.1, 137:2,
137:22].
Same words as in 5.1 are also in OpenMP 5.2 in "10.4 simd Construct"
[235:31].
Did I miss something? If so, can you provide the example?
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
prev parent reply other threads:[~2022-12-15 20:53 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
2022-12-15 20:53 ` Tobias Burnus [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=656ea043-b4aa-dad3-1806-3145320623c2@codesourcery.com \
--to=tobias@codesourcery.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).