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/109767] [OpenMP][5.2] Missing loop-variable privatization inside 'teams'
Date: Mon, 08 May 2023 14:41:54 +0000	[thread overview]
Message-ID: <bug-109767-4-76G6mc0gcg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109767-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Even
subroutine foo
  integer :: i, j
  !$omp parallel
  do i = 1, 10
    do j = 1, 10
    end do
  end do
  !$omp end parallel
end subroutine
subroutine bar
  integer :: i, j
  !$omp teams
  do i = 1, 10
    do j = 1, 10
    end do
  end do
  !$omp end teams
end subroutine
subroutine baz
  integer :: i, j
  !$omp parallel
  !$omp loop bind(parallel)
  do i = 1, 10
    do j = 1, 10
    end do
  end do
  !$omp end parallel
end subroutine
subroutine qux
  integer :: i, j
  !$omp teams
  !$omp loop bind(teams)
  do i = 1, 10
    do j = 1, 10
    end do
  end do
  !$omp end teams
end subroutine
has
grep private pr109767.f90.005t.original 
  #pragma omp parallel private(i) private(j)
  #pragma omp teams private(i) private(j)
  #pragma omp parallel private(j)
  #pragma omp teams private(j)

  parent reply	other threads:[~2023-05-08 14:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08  9:10 [Bug middle-end/109767] New: " burnus at gcc dot gnu.org
2023-05-08 14:27 ` [Bug middle-end/109767] " jakub at gcc dot gnu.org
2023-05-08 14:41 ` jakub at gcc dot gnu.org [this message]
2023-05-08 15:20 ` burnus at gcc dot gnu.org
2023-05-08 15:29 ` jakub at gcc dot gnu.org
2023-05-08 15:51 ` jakub at gcc dot gnu.org

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-109767-4-76G6mc0gcg@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).