This term is used in exactly three places
omp_target_is_present
omp_target_associate_ptr
omp_target_disassociate_ptr
This looks like it is trying to allow for OpenCL-like buffer behavior, but the term 'device buffer' is nowhere defined or used when describing the map clauses, which would be appropriate. It's a peculiar term to use here.
device buffer
Comments and discussion of the 4.1 OpenMP Draft specifications. Comment period ends September 30, 2015. See http://openmp.org/wp/openmp-specifications/ to download the specifications. (Read Only)
Return to “OpenMP 4.1 DRAFT - Public Comments”
Jump to
- Using OpenMP
- Conferences and Events
- OpenMP 5.0 API Specifications
- OpenMP 5.0 Examples Discussion
- TR9 - OpenMP 5.1 Draft Discussion
- OpenMP 4.5 Examples Discussion
- OpenMP 4.5 API Specifications
- Using OpenMP - The Book and Examples
- OpenMP 4.0 Examples
- TR8 - OpenMP 5.1 Draft Discussion
- TR7 - OpenMP 5.0 Draft Discussion
- TR6 - OpenMP 5.0 Draft Discussion
- TR5 Memory Management Discussion
- TR4 OpenMP 5.0 Preview Discussion
- OpenMP 4.1 DRAFT - Public Comments
- OpenMP 4.0 API Specifications
- TR2 and TR3 Discussion
- OpenMP 3.0 API Specifications
- OpenMP 4.0 Public Review Release Candidates
- OpenMP 3.1 API Specifications
- Draft 3.1 Public Comment
- Draft 3.0 Public Comment