tra added a comment. In D81713#2090309 <https://reviews.llvm.org/D81713#2090309>, @arsenm wrote:
> > I can tell that it does not. We're still looking under `/opt/rocm` by > > default. I've ran into it trying to get comgr working with the recent LLVM > > which prompted my comment on Github > > <https://github.com/llvm/llvm-project/commit/123bee602a260150ff55c74287f583a67ee78f36#r39817848> > > Not sure how that would be related to comgr? comgr doesn't rely on the > dynamic path and embeds the bitcode in the library. The comgr build finds the > libraries through cmake and doesn't care where they're located The version I have (~3.2. I should update it, maybe 3.5 is different) uses libclang (built from LLVM tree close to HEAD), creates Driver() instance and that driver instance goes through the motions trying to find ROCm installation and fails. Clang itself also fails the same way -- there's no /opt/rocm/amdgcn/bitcode/ it's looking for. CHANGES SINCE LAST ACTION https://reviews.llvm.org/D81713/new/ https://reviews.llvm.org/D81713 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
