Re: Problematic 'target teams' libgomp tests

2016-01-14 Thread Jakub Jelinek
On Thu, Jan 14, 2016 at 07:08:23PM +0300, Alexander Monakov wrote: > On Thu, 14 Jan 2016, Jakub Jelinek wrote: > > That is weird, because c is also a firstprivate var in target and > > (implicitly) shared in teams, so if omp lowering/expansion is not buggy, > > you should see the exactly same probl

Re: Problematic 'target teams' libgomp tests

2016-01-14 Thread Alexander Monakov
On Thu, 14 Jan 2016, Jakub Jelinek wrote: > That is weird, because c is also a firstprivate var in target and > (implicitly) shared in teams, so if omp lowering/expansion is not buggy, > you should see the exactly same problem with that. > Wonder if we use GOMP_MAP_FIRSTPRIVATE_INT when we shouldn'

Re: Problematic 'target teams' libgomp tests

2016-01-14 Thread Jakub Jelinek
On Wed, Jan 13, 2016 at 09:05:47PM +0300, Alexander Monakov wrote: > I'm testing 'target teams' implementation for gomp-nvptx branch, and I'm > seeing test failures that, I think, are caused by faulty tests (unlike NVPTX, > MIC offloading uses 1 team similar to native execution, so the issues are n

Problematic 'target teams' libgomp tests

2016-01-13 Thread Alexander Monakov
Hello, I'm testing 'target teams' implementation for gomp-nvptx branch, and I'm seeing test failures that, I think, are caused by faulty tests (unlike NVPTX, MIC offloading uses 1 team similar to native execution, so the issues are not exposed there). First, there's libgomp.c/target-31.c where th