diff options
| author | Shilei Tian <i@tianshilei.me> | 2022-11-04 19:40:45 +0300 |
|---|---|---|
| committer | Shilei Tian <i@tianshilei.me> | 2022-11-04 19:41:09 +0300 |
| commit | 8eab182bf2b7683fb5637a01b7664b802c759c2f (patch) | |
| tree | 01a936c336d65d2be1455bbd16a5c49d305d799f /openmp | |
| parent | a032b47e7e7792d57a26c0dcb38ecd12c28a0248 (diff) | |
[RFC][OpenMP][Doc] No backward compatible for libomptarget and plugins
Now we state that backward compatibility is not guaranteed in the document.
Reviewed By: JonChesterfield, dreachem
Differential Revision: https://reviews.llvm.org/D133277
Diffstat (limited to 'openmp')
| -rw-r--r-- | openmp/docs/SupportAndFAQ.rst | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/openmp/docs/SupportAndFAQ.rst b/openmp/docs/SupportAndFAQ.rst index dc1ad83902d2..8bf0ea56a7ae 100644 --- a/openmp/docs/SupportAndFAQ.rst +++ b/openmp/docs/SupportAndFAQ.rst @@ -413,3 +413,17 @@ linkable device image. clang++ openmp.cpp -fopenmp --offload-arch=sm_80 -c clang++ cuda.cu --offload-new-driver --offload-arch=sm_80 -fgpu-rdc -c clang++ openmp.o cuda.o --offload-link -o app + +Q: Are libomptarget and plugins backward compatible? +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +No. libomptarget and plugins are now built as LLVM libraries starting from LLVM +15. Because LLVM libraries are not backward compatible, libomptarget and plugins +are not as well. Given that fact, the interfaces between 1) the Clang compiler +and libomptarget, 2) the Clang compiler and device runtime library, and +3) libomptarget and plugins are not guaranteed to be compatible with an earlier +version. Users are responsible for ensuring compatibility when not using the +Clang compiler and runtime libraries from the same build. Nevertheless, in order +to better support third-party libraries and toolchains that depend on existing +libomptarget entry points, contributors are discouraged from making +modifications to them. |