[Bug c/70688] bogus OpenACC data clause errors involving reductions

2016-06-01 Thread cesar at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70688

cesar at gcc dot gnu.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from cesar at gcc dot gnu.org ---
Fixed in r237011.

[Bug c/70688] bogus OpenACC data clause errors involving reductions

2016-06-01 Thread cesar at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70688

--- Comment #3 from cesar at gcc dot gnu.org ---
Author: cesar
Date: Wed Jun  1 20:40:10 2016
New Revision: 237012

URL: https://gcc.gnu.org/viewcvs?rev=237012=gcc=rev
Log:
PR c/70688
* pr70688.c: New file.


Added:
   
branches/gomp-4_0-branch/libgomp/testsuite/libgomp.oacc-c-c++-common/pr70688.c
Modified:
branches/gomp-4_0-branch/libgomp/ChangeLog.gomp

[Bug c/70688] bogus OpenACC data clause errors involving reductions

2016-06-01 Thread cesar at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70688

--- Comment #2 from cesar at gcc dot gnu.org ---
Author: cesar
Date: Wed Jun  1 20:37:44 2016
New Revision: 237011

URL: https://gcc.gnu.org/viewcvs?rev=237011=gcc=rev
Log:
PR c/70688
* pr70688.c: New file.


Added:
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/pr70688.c
Modified:
trunk/libgomp/ChangeLog

[Bug c/70688] bogus OpenACC data clause errors involving reductions

2016-06-01 Thread cesar at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70688

--- Comment #1 from cesar at gcc dot gnu.org ---
Created attachment 38621
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38621=edit
new test case

This issue has been resolved in trunk r236678. I forgot to include a PR tag in
the ChangeLog entry. 

To verify the fix, I modified the original test case to make it executable in
the libgomp test suite. Furthermore, I changed parallel regions to parallel
loop regions so that the reduction yields sane results with multiple gangs.
I'll commit this test case to trunk with the proper PR tag in the ChangeLog
entry before I close this issue.