[llvm-bugs] [Bug 41767] OpenMP default(none) + schedule(dynamic, variable) - difference with gcc
via llvm-bugs
llvm-bugs at lists.llvm.org
Thu May 9 03:47:55 PDT 2019
https://bugs.llvm.org/show_bug.cgi?id=41767
Roman Lebedev <lebedev.ri at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jdoerfert at anl.gov
Status|RESOLVED |REOPENED
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=90406
Resolution|FIXED |---
--- Comment #3 from Roman Lebedev <lebedev.ri at gmail.com> ---
... and i had to revert this & the other commit. Sorry :(
This implementation isn't sound as per the standard.
It erroneously diagnoses e.g. the following case:
```
$ cat test.cpp
void f(int n) {
#pragma omp parallel default(none) if(n)
;
}
```
```
$ ./bin/clang -fopenmp test.cpp
test.cpp:2:40: error: variable 'n' must have explicitly specified data sharing
attributes
#pragma omp parallel default(none) if(n)
^
test.cpp:2:31: note: explicit data sharing attribute requested here
#pragma omp parallel default(none) if(n)
^
1 error generated.
```
As per OpenMP Application Programming Interface Version 5.0 November 2018:
* 2.19.4.1default Clause
The default clause explicitly determines the data-sharing attributes of
variables that are referenced *in a parallel, teams, or task generating
construct and would otherwise be implicitly determined
(see Section 2.19.1.1 on page 270).
* 2.6.1 Determining the Number of Threads for a parallel Region
Using a variable in an if or num_threads clause expression of a parallel
construct causes an implicit reference to the variable in all enclosing
constructs. The if clause expression and the num_threads clause expression
are evaluated in the context outside of the parallel construct,
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190509/6cfc2cc3/attachment.html>
More information about the llvm-bugs
mailing list