From: Thomas Schwinge <thomas@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Cesar Philippidis <cesar@codesourcery.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [patch,gomp4] error on invalid acc loop clauses
Date: Wed, 20 May 2015 09:41:00 -0000 [thread overview]
Message-ID: <87k2w3iogr.fsf@schwinge.name> (raw)
In-Reply-To: <20150520084327.GB1751@tucnak.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
Hi!
On Wed, 20 May 2015 10:43:27 +0200, Jakub Jelinek <jakub@redhat.com> wrote:
> On Wed, May 20, 2015 at 10:23:21AM +0200, Thomas Schwinge wrote:
> > I see that some checking is also being done gcc/omp-low.c:scan_omp_for:
> > »gang, worker and vector may occur only once in a loop nest«, and »gang,
> > worker and vector must occur in this order in a loop nest«. Don't know
> > if that conceptually also belongs into
> > gcc/omp-low.c:check_omp_nesting_restrictions?
>
> Doesn't look like anything related to construct/region nesting...
It is checking invalid nesting of loop constructs, for example:
#pragma acc loop gang
for [...]
{
#pragma acc loop gang // gang, worker and vector may occur only once in a loop nest
for [...]
..., or:
#pragma acc loop vector
for [...]
{
#pragma acc loop gang // gang, worker and vector must occur in this order in a loop nest
for [...]
..., and so on.
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2015-05-20 9:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <555A05BA.3050001@mentor.com>
2015-05-19 8:04 ` [gomp4] bootstrap broken, function enclosing_target_ctx defined but not used Tom de Vries
2015-05-15 18:14 ` [patch,gomp4] error on invalid acc loop clauses Cesar Philippidis
2015-05-20 7:48 ` [gomp4] bootstrap broken, function enclosing_target_ctx defined but not used Thomas Schwinge
2015-05-20 8:24 ` [patch,gomp4] error on invalid acc loop clauses Thomas Schwinge
2015-05-20 8:56 ` Jakub Jelinek
2015-05-20 9:41 ` Thomas Schwinge [this message]
2015-05-20 10:01 ` Jakub Jelinek
2015-05-20 14:19 ` Cesar Philippidis
2015-05-20 14:36 ` Jakub Jelinek
2015-05-20 23:35 ` Cesar Philippidis
2015-06-03 0:03 ` [ping] " Cesar Philippidis
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=87k2w3iogr.fsf@schwinge.name \
--to=thomas@codesourcery.com \
--cc=cesar@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
/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).