public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/64765] New: [OpenACC] Bogus "'copy' is not valid for '#pragma acc kernels loop'"
@ 2015-01-24 10:07 burnus at gcc dot gnu.org
  2015-10-08 15:57 ` [Bug c/64765] " tschwinge at gcc dot gnu.org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: burnus at gcc dot gnu.org @ 2015-01-24 10:07 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 64765
           Summary: [OpenACC] Bogus "'copy' is not valid for '#pragma acc
                    kernels loop'"
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Keywords: openacc, rejects-valid
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: burnus at gcc dot gnu.org
                CC: tschwinge at gcc dot gnu.org

The following program gives

foo.c:2:36: error: 'copy' is not valid for '#pragma acc kernels loop'
foo.c:2:26: error: 'create' is not valid for '#pragma acc kernels loop'
 #pragma acc kernels loop create(f) copy(r)
                          ^

I believe copy and create are invalid for LOOP but they should be valid for
KERNELS - and, hence, also for KERNEL LOOPS. (The equivalent Fortran program
compiles.)


Test case:

void foo(float *f, double *r) {
#pragma acc kernels loop create(f) copy(r)
for(;;) {}
}


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2015-10-27  8:42 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-01-24 10:07 [Bug c/64765] New: [OpenACC] Bogus "'copy' is not valid for '#pragma acc kernels loop'" burnus at gcc dot gnu.org
2015-10-08 15:57 ` [Bug c/64765] " tschwinge at gcc dot gnu.org
2015-10-27  8:39 ` tschwinge at gcc dot gnu.org
2015-10-27  8:42 ` tschwinge at gcc dot gnu.org

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).