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 fortran/62007] default(none) conflicts with iteration variable in openmp parallel loop simd
Date: Mon, 08 Dec 2014 13:32:00 -0000	[thread overview]
Message-ID: <bug-62007-4-2BTLUpDhZz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62007-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I think the message is correct, or at least the case is highly unclear, the
OpenMP 4.0 standard has various unclear corner cases.
The thing is, the loop iterator is predetermined linear, and the linear clause
makes implicit reference to the outer var, but as linear clause is not allowed
on the parallel, it can't be specified there and with default(none) you are
requesting that everything is specified there explicitly.
I can only suggest using non-combined construct in that case if you for some
reason need default(none), say:
!$omp parallel private (i_ct) default(none)
!$omp do simd
  do i_ct = 1, 10
    ...
  end do
!$omp end parallel
or so.


      parent reply	other threads:[~2014-12-08 13:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04 10:48 [Bug fortran/62007] New: " alexander.grund at mailbox dot tu-dresden.de
2014-08-04 10:48 ` [Bug fortran/62007] " alexander.grund at mailbox dot tu-dresden.de
2014-08-04 10:53 ` dominiq at lps dot ens.fr
2014-08-04 11:02 ` alexander.grund at mailbox dot tu-dresden.de
2014-08-04 11:02 ` alexander.grund at mailbox dot tu-dresden.de
2014-08-04 11:04 ` alexander.grund at mailbox dot tu-dresden.de
2014-08-04 12:29 ` anlauf at gmx dot de
2014-08-04 12:36 ` alexander.grund at mailbox dot tu-dresden.de
2014-12-06 22:13 ` dominiq at lps dot ens.fr
2014-12-08 13:32 ` 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-62007-4-2BTLUpDhZz@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).