public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/106504] [OpenMP] 'for simd linear(i:1)' should be rejected with 'parallel private(i)'
Date: Wed, 10 Aug 2022 07:40:55 +0000	[thread overview]
Message-ID: <bug-106504-4-kQzieA0hPn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106504-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106504

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
There have been discussions about this in several F2Fs.
For linear it is desirable to allow private outer var because linear
is the implicit behavior of simd iterators and people want to be able to use
them
even if they are private outer (say even simple
void foo (int *a) { int i;
#pragma omp simd
for (i = 0; i < 16; i++)
a[i] = i;
}
would be then invalid).
Some people wanted to just drop the requirements even for lastprivate etc.
(silently not assign to outer var).

      reply	other threads:[~2022-08-10  7:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02 11:02 [Bug middle-end/106504] New: " burnus at gcc dot gnu.org
2022-08-10  7:40 ` jakub at gcc dot gnu.org [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=bug-106504-4-kQzieA0hPn@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).