[Openmp-commits] [PATCH] D133277: [RFC][OpenMP][Doc] No backward compatible for libomptarget and plugins

Shilei Tian via Phabricator via Openmp-commits openmp-commits at lists.llvm.org
Wed Oct 5 05:49:24 PDT 2022


tianshilei1992 updated this revision to Diff 465360.
tianshilei1992 added a comment.

fix comments


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D133277/new/

https://reviews.llvm.org/D133277

Files:
  openmp/docs/SupportAndFAQ.rst


Index: openmp/docs/SupportAndFAQ.rst
===================================================================
--- openmp/docs/SupportAndFAQ.rst
+++ openmp/docs/SupportAndFAQ.rst
@@ -329,3 +329,17 @@
 stack memory during execution and crash. The environment variable
 ``LIBOMPTARGET_STACK_SIZE`` can be used to increase the stack size if this
 occurs.
+
+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.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: D133277.465360.patch
Type: text/x-patch
Size: 1218 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/openmp-commits/attachments/20221005/d8e81475/attachment.bin>


More information about the Openmp-commits mailing list