[Openmp-commits] [PATCH] D138002: [OpenMP][libomptarget] Build plugins-nextgen/common/PluginInterface with protected visibility

Kevin Sala Penadés via Phabricator via Openmp-commits openmp-commits at lists.llvm.org
Sun Dec 4 03:28:41 PST 2022

kevinsala added a comment.

In D138002#3969020 <https://reviews.llvm.org/D138002#3969020>, @jhuber6 wrote:

> In D138002#3969018 <https://reviews.llvm.org/D138002#3969018>, @tianshilei1992 wrote:
>> In D138002#3969003 <https://reviews.llvm.org/D138002#3969003>, @jhuber6 wrote:
>>> In D138002#3969000 <https://reviews.llvm.org/D138002#3969000>, @tianshilei1992 wrote:
>>>> Currently I'm still encountering the issue that, the function call to `__tgt_rtl_is_valid_binary` in `__tgt_rtl_is_valid_binary_info` jumps to another plugin.
>>> Can you check if that symbol is actually protected in the `.so` you're using?
>> They are not protected.
>>   ➜  readelf -s /home/ac.shilei.tian/Documents/build/openmp/debug/lib/libomptarget.rtl.x86_64.nextgen.so | rg is_va
>>    77783: 000000000046b7b0   472 FUNC    GLOBAL DEFAULT   12 __tgt_rtl_is_val[...]
>>    77866: 000000000046b710   157 FUNC    GLOBAL DEFAULT   12 __tgt_rtl_is_val[...]
> That's weird, the CMake should have the visibility preset for all of those libraries as far as I can tell. Think you could check the flags it's using to build the library?

@tianshilei1992 Could you attach the call stack trace too? Thanks!

  rG LLVM Github Monorepo



More information about the Openmp-commits mailing list