summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/thread
diff options
context:
space:
mode:
authorSamuel Antao <sfantao@us.ibm.com>2016-01-19 20:40:49 +0000
committerSamuel Antao <sfantao@us.ibm.com>2016-01-19 20:40:49 +0000
commit23abd726e66f44bf1f59c8c23830dd3ea4242b23 (patch)
treea3aba04470b2dd1b0478653024869470a8d2e8ff /lldb/packages/Python/lldbsuite/test/python_api/thread
parent311f27c0a8f637cdbc46c5ccf7f9e59854503788 (diff)
downloadbcm5719-llvm-23abd726e66f44bf1f59c8c23830dd3ea4242b23.tar.gz
bcm5719-llvm-23abd726e66f44bf1f59c8c23830dd3ea4242b23.zip
[OpenMP] Detect implicit map type to report unspecified map type for target enter/exit data directives.
Support for the following OpenMP 4.5 restriction on 'target enter data' and 'target exit data': - A map-type must be specified in all map clauses. I have to save 'IsMapTypeImplicit' when parsing a map clause to support this constraint and for more informative error messages. This helps me support the following case: #pragma omp target enter data map(r) // expected-error {{map type must be specified for '#pragma omp target enter data'}} and distinguish it from: #pragma omp target enter data map(tofrom: r) // expected-error {{map type 'tofrom' is not allowed for '#pragma omp target enter data'}} Patch by Arpith Jacob. Thanks! llvm-svn: 258179
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud