[llvm-bugs] [Bug 40664] New: Allow multiple copies of OpenMP runtime loaded in memory

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=40664

            Bug ID: 40664
           Summary: Allow multiple copies of OpenMP runtime loaded in
                    memory
           Product: OpenMP
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Runtime Library
          Assignee: unassignedbugs at nondot.org
          Reporter: atilag at gmail.com
                CC: llvm-bugs at lists.llvm.org

There seems to be a limitation in the OpenMP Runtime in which multiple copies
of the Runtime are not allowed for the same process [1].
This renders the usage of OpenMP through clang almost useless in some
situations where you don't have control over what other libraries are being
loaded into you process, like for example creating Python extensions (which are
loaded dynamically at runtime by common Python runtimes). C++ is being used
extensively here, and we cannot control what other libraries will be loaded so
there can exists situations where other extensions are using OpenMP so clashing
with your extension.
The thing is that this problem doesn't seem to exist using gcc libgomp
implementation, so I was wondering whether reviewing this limitation to get rid
of it worths the effort (as it sounds like a complex achievement). Python
extensions are a huge soure for clang users so I guess that it makes sense to
at least try to tackle this.

Thanks for your work!


[1]
https://github.com/llvm/llvm-project/blob/57b08b0944046a6a57ee9b7b479181f548a5b9b4/openmp/runtime/src/i18n/en_US.txt#L449

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190208/23dfa3bf/attachment-0001.html>