Open tgymnich opened 11 months ago
@llvm/issue-subscribers-openmp
Author: Tim Gymnich (tgymnich)
@jhuber6 is this fixed by your patch not to include LLVM options for runtimes?
@jhuber6 is this fixed by your patch not to include LLVM options for runtimes?
I got it on a debug build before that patch, and after pulling it seems to have gone away. Can you confirm @tgymnich?
@jhuber6 The issue seems fixed on main. Shall we close #73249 then?
@jhuber6 The issue seems fixed on main. Shall we close #73249 then?
Yeah this was probably due to picking up some configurations from another project. Hopefully we can keep things cleaner now. Go ahead and close that revision if you no longer need it. Thanks for confirming.
Any update on this issue? Since https://github.com/llvm/llvm-project/pull/73031 is reverted,
Not as far as I know. It might still be a good idea to merge https://github.com/llvm/llvm-project/pull/73249 as a stop-gap solution for now, while we look for a solution for #73031
I think this is a more general problem. I've seen it manifest in some of AMD's builds recently. Seems there might be a bug in the GCC12 headers that changes the visibility of the assert function.
Enabling libstdc++ assertions (
-D_GLIBCXX_ASSERTIONS
) introduces an unwanted dependency on libstdc++ for libomp. This causes a linker error when building libomp with assertions enabled (-DLLVM_ENABLE_ASSERTIONS=ON
) when using libstdc++ >= 12.Build error:
How To Reproduce:
Here is a Dockerfile to reproduce the issue.
Related issues: