- Call llvm_process_pass_plugin from clang when in standalone mode
- bug spotted in https://github.com/llvm/llvm-project/issues/120 and recorded as https://bugs.llvm.org/show_bug.cgi?id=44870
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Unit Tests
Time | Test | |
---|---|---|
10 ms | LLVM.Bindings/Go::Unknown Unit Message ("") |
Event Timeline
Comment Actions
I don't know enough about the cmake and dylib build to properly review this. Maybe Tom can help?
Please add a mention of https://github.com/llvm/llvm-project/issues/120 / https://bugs.llvm.org/show_bug.cgi?id=44870 in the change description.
Comment Actions
tested with
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/tmp/inst -DLLVM_LINK_LLVM_DYLIB=ON -DLLVM_BUILD_LLVM_DYLIB=ON -DLLVM_POLLY_LINK_INTO_TOOLS=ON -DLLVM_TOOL_POLLY_BUILD=ON -DPOLLY_BUNDLED_ISL=ON ../llvm && make -j30 && nm -DC lib/libLLVM-11git.so | grep getPollyPluginInfo
Comment Actions
Also pass with
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/tmp/inst -DLLVM_LINK_LLVM_DYLIB=OFF -DLLVM_BUILD_LLVM_DYLIB=OFF -DLLVM_POLLY_LINK_INTO_TOOLS=ON -DLLVM_TOOL_POLLY_BUILD=ON -DPOLLY_BUNDLED_ISL=ON ../llvm && make -j30 && make check-polly -j20
(i.e. when no using DYLIB but still linking polly statically)
and
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/tmp/inst -DLLVM_LINK_LLVM_DYLIB=OFF -DLLVM_BUILD_LLVM_DYLIB=OFF -DLLVM_POLLY_LINK_INTO_TOOLS=OFF -DLLVM_TOOL_POLLY_BUILD=ON -DPOLLY_BUNDLED_ISL=ON ../llvm && make -j30 && make check-polly -j20
(i.e. when not using dylib and not linking polly statically)
and
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/tmp/inst -DLLVM_LINK_LLVM_DYLIB=ON -DLLVM_BUILD_LLVM_DYLIB=ON -DLLVM_POLLY_LINK_INTO_TOOLS=OFF -DLLVM_TOOL_POLLY_BUILD=ON -DPOLLY_BUNDLED_ISL=ON ../llvm && make -j30 && make check-polly -j20
(i.e. when using dylib but without polly linked in statically)
Comment Actions
But it fails (registered twice) when using LLVM_ENABLE_PROJECTS instead... That's definitively a lot of configuration :-
Actually a configuration issue on my side, everything works file with that config too.