derek.holloway
7502bf64a4
CodeQL / Analyze (actions) (push) Canceled after 0s
CodeQL / Analyze (python) (push) Canceled after 0s
pre-commit / pre-commit (push) Canceled after 0s
Multi-Arch CI / setup (push) Canceled after 0s
Publish build_manylinux_x86_64 images / publish_build_manylinux_x86_64 (push) Canceled after 0s
Setup (Multi-Arch) / setup (push) Canceled after 0s
Multi-Arch CI / Linux::${{ fromJSON(needs.setup.outputs.linux_build_config || '{}').build_variant_label || 'skip' }} (push) Canceled after 0s
Publish TheRock Docker image / build-and-push-image (push) Canceled after 0s
Publish no_rocm_image_ubi10 image / publish_no_rocm_image_ubi10 (push) Canceled after 0s
Multi-Arch CI / Windows::${{ fromJSON(needs.setup.outputs.windows_build_config || '{}').build_variant_label || 'skip' }} (push) Canceled after 0s
Publish TheRock Docker image / build-and-push-image (push) Canceled after 0s
Multi-Arch CI / Manifest Diff (push) Canceled after 0s
TheRock Manifest Diff Report / Generate Manifest Diff Report (push) Canceled after 0s
Multi-Arch CI / CI Summary (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04 images / publish_no_rocm_image_ubuntu24_04 (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04_ocl_rt images / publish_no_rocm_image_ubuntu24_04_ocl_rt (push) Canceled after 0s
Publish TheRock Docker image / build-and-push-image (push) Canceled after 0s
Publish TheRock Docker image / build-and-push-image (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04 images / publish_no_rocm_image_ubuntu24_04_rocgdb (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04_rocgdb images / publish_no_rocm_image_ubuntu24_04_rocgdb (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04 images / publish_no_rocm_image_ubuntu24_04_ocl_rt (push) Canceled after 0s
Publish TheRock Docker image / build-and-push-image (push) Canceled after 0s
Unit Tests / Unit Tests :: ubuntu-24.04 (push) Canceled after 0s
Unit Tests / Unit Tests :: windows-2022 (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04 images / publish_no_rocm_image_ubuntu24_04_media (push) Canceled after 0s
Unit Tests / Unit Tests Summary (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04 images / publish_no_rocm_image_ubuntu24_04_openmpi (push) Canceled after 0s
27 lines
1.5 KiB
ReStructuredText
27 lines
1.5 KiB
ReStructuredText
.. _omp100:
|
|
.. _omp_no_external_caller_in_target_region:
|
|
|
|
Potentially unknown OpenMP target region caller `[OMP100]`
|
|
==========================================================
|
|
|
|
A function remark that indicates the function, when compiled for a GPU, is
|
|
potentially called from outside the translation unit. Note that a remark is
|
|
only issued if we tried to perform an optimization which would require us to
|
|
know all callers on the GPU.
|
|
|
|
To facilitate OpenMP semantics on GPUs we provide a runtime mechanism through
|
|
which the code that makes up the body of a parallel region is shared with the
|
|
threads in the team. Generally we use the address of the outlined parallel
|
|
region to identify the code that needs to be executed. If we know all target
|
|
regions that reach the parallel region we can avoid this function pointer
|
|
passing scheme and often improve the register usage on the GPU. However, If a
|
|
parallel region on the GPU is in a function with external linkage we may not
|
|
know all callers statically. If there are outside callers within target
|
|
regions, this remark is to be ignored. If there are no such callers, users can
|
|
modify the linkage and thereby help optimization with a `static` or
|
|
`__attribute__((internal))` function annotation. If changing the linkage is
|
|
impossible, e.g., because there are outside callers on the host, one can split
|
|
the function into an external visible interface which is not compiled for
|
|
the target and an internal implementation which is compiled for the target
|
|
and should be called from within the target region.
|