You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
…ary (#1240)
This is to solve #1236
This commit hides the symbols of the shared libraries for
`libtriton.so`, so that when other object link against `libtriton.so`,
it won't have confilct.
It hides the symbols of the shared libraries for libtriton.so, so that when other object link against libtriton.so, there won't have conflict.
This PR didn't handle the case in MacOS, but there is a possible way to use exported_symbols_lists to export a whitelist symbols as mxnet/CMakeLists.txt. I put here in case anyone needs it.
pingzhuu
pushed a commit
to siliconflow/triton
that referenced
this issue
Apr 2, 2024
…ary (triton-lang#1240)
This is to solve triton-lang#1236
This commit hides the symbols of the shared libraries for
`libtriton.so`, so that when other object link against `libtriton.so`,
it won't have confilct.
The symbols of LLVM/MLIR are exported by libtriton.so. These symbols may alias to the other components which uses different LLVM/MLIR infrastructure.
And cause issue like:
llvm/llvm-project#47565
A suggested solution is to strip all the LLVM/MLIR symbol from libtriton.so to isolate the LLVM infrastructure.
https://stackoverflow.com/questions/2222162/how-to-apply-fvisibility-option-to-symbols-in-static-libraries
The text was updated successfully, but these errors were encountered: