Hi Jakub! On Wed, 5 Jun 2019 12:00:25 +0200, Jakub Jelinek <ja...@redhat.com> wrote: > On Wed, Jun 05, 2019 at 11:25:07AM +0200, Thomas Schwinge wrote: > > + !$omp target map(to: a) map(tofrom: b, c, d) map(from: e) > > + !$acc parallel copyin(a) copy(b, c, d) copyout(e) > > Is mixing OpenMP and OpenACC construct this way defined at all?
It's not. I'm using this just to avoid duplicating the test case file, that is, '-fopenacc' and '-fopenmp' aren't enabled at the same time. > I see we reject OpenMP constructs inside of OpenACC contexts ACK. > and > using OpenACC constructs inside host OpenMP constructs should be generally > fine too ACK. (Should, but currently isn't.) > but mixing OpenMP offloading constructs with OpenACC constructs > sounds wrong. ACK. (Unless that gets defined by the two standards.) Grüße Thomas
signature.asc
Description: PGP signature
