<div>Just another follow-up, seems like ExecutionEngine is still not usable without editing CMakeLists, on my setup I had to edit CMakeLists.txt as well to get the example working.</div><div>Below is the modifications I made:</div><div><br></div><div>Modified Hello.cpp for testing:</div><div>```</div><div><div> bool runOnFunction(Function &F) override {</div><div> ++HelloCounter;</div><div> std::string errStr;</div><div> EngineBuilder eb;</div><div> eb.setErrorStr(&errStr);</div><div> eb.setEngineKind(EngineKind::Kind::JIT);</div><div> ExecutionEngine* ee=eb.create();</div><div> errs()<<"ExecutionEngine:"<<ee<<" Error:"<<errStr<<"\n";</div><div> delete ee;</div><div> errs() << "Hello: ";</div><div> errs().write_escaped(F.getName()) << '\n';</div><div> return false;</div><div> }</div></div><div>```</div><div><br></div><div>Modified opt's CMakeLists.txt:</div><div><br></div><div>```</div><div><div><div>set(LLVM_LINK_COMPONENTS</div><div> ${LLVM_TARGETS_TO_BUILD}</div><div> AggressiveInstCombine</div><div> Analysis</div><div> BitWriter</div><div> CodeGen</div><div> Core</div><div> MC</div><div> MCJIT</div><div> Object</div><div> OrcJIT</div><div> Interpreter</div><div> RuntimeDyld</div><div> Coroutines</div><div> IPO</div><div> IRReader</div><div> InstCombine</div><div> Instrumentation</div><div> MC</div><div> ObjCARCOpts</div><div> ScalarOpts</div><div> Support</div><div> Target</div><div> TransformUtils</div><div> Vectorize</div><div> Passes</div><div> ExecutionEngine</div><div> )</div><div><br></div><div># Support plugins.</div><div>set(LLVM_NO_DEAD_STRIP 1)</div><div><br></div><div>add_llvm_tool(opt</div><div> AnalysisWrappers.cpp</div><div> BreakpointPrinter.cpp</div><div> Debugify.cpp</div><div> GraphPrinters.cpp</div><div> NewPMDriver.cpp</div><div> PassPrinters.cpp</div><div> PrintSCC.cpp</div><div> opt.cpp</div><div><br></div><div> DEPENDS</div><div> intrinsics_gen</div><div> )</div><div>export_executable_symbols(opt)</div><div><br></div><div>if(WITH_POLLY AND LINK_POLLY_INTO_TOOLS)</div><div> target_link_libraries(opt PRIVATE Polly)</div><div>endif(WITH_POLLY AND LINK_POLLY_INTO_TOOLS)</div><div>target_link_libraries(opt PUBLIC LLVMExecutionEngine)</div></div></div><div><br></div><div>```</div><div><br></div><div>Modified opt's LLVMBuild.txt:</div><div><br></div><div>```</div><div><div>;===- ./tools/opt/LLVMBuild.txt --------------------------------*- Conf -*--===;</div><div>;</div><div>; The LLVM Compiler Infrastructure</div><div>;</div><div>; This file is distributed under the University of Illinois Open Source</div><div>; License. See LICENSE.TXT for details.</div><div>;</div><div>;===------------------------------------------------------------------------===;</div><div>;</div><div>; This is an LLVMBuild description file for the components in this subdirectory.</div><div>;</div><div>; For more information on the LLVMBuild system, please see:</div><div>;</div><div>; http://llvm.org/docs/LLVMBuild.html</div><div>;</div><div>;===------------------------------------------------------------------------===;</div><div><br></div><div>[component_0]</div><div>type = Tool</div><div>name = opt</div><div>parent = Tools</div><div>required_libraries =</div><div> AsmParser</div><div> BitReader</div><div> BitWriter</div><div> CodeGen</div><div> IRReader</div><div> IPO</div><div> Instrumentation</div><div> Scalar</div><div> ObjCARC</div><div> Passes</div><div> ExecutionEngine</div><div> Interpreter</div><div> MCJIT</div><div> Native</div><div> NativeCodeGen</div><div> all-targets</div></div><div><br></div><div>```</div><div><br></div><div>On top of that I also added these lines to the beginning of main function in opt.cpp to force linking ExecutionEngine:</div><div><br></div><div>```</div><div><div> if(argc==-1){</div><div> EngineBuilder eb;</div><div> ExecutionEngine* ee=eb.create();</div><div> delete ee;</div><div> }</div></div><div>```</div><div><br></div><div>as well as force linking MCJIT and Interpreter by including headers in opt:</div><div><br></div><div>```</div><div><div>#include "llvm/ExecutionEngine/ExecutionEngine.h"</div><div>#include "llvm/ExecutionEngine/Interpreter.h"</div><div>#include "llvm/ExecutionEngine/MCJIT.h"</div></div><div>```</div><div><br></div><div>Moving cl::parseCommandLineOptions doesn't seem to be related to the issue, my previous assumption was wrong.</div><div><br></div><div>Those modifications works at least on my setup with the following output:</div><div><br></div><div>```</div><div><div>λ : >>> bin/opt -load lib/LLVMHello.dylib hw.ll -hello</div><div>WARNING: You're attempting to print out a bitcode file.</div><div>This is inadvisable as it may cause display problems. If</div><div>you REALLY want to taste LLVM bitcode first-hand, you</div><div>can force output with the `-f' option.</div><div><br></div><div>Assertion failed: (M && "Module is null?"), function Init, file /Users/naville/Development/Hikari/lib/ExecutionEngine/ExecutionEngine.cpp, line 80.</div></div><div><br></div><div>```</div><div><br></div><div>Which is due to i didn't initialize the EEBuilder properly, but at least the pass now loads and executes properly</div><div><br></div><div><br></div><div>Zhang</div><div><br></div><div><br></div><div><br></div><div><includetail><div> </div><div> </div><div style="font:Verdana normal 14px;color:#000;"><div style="FONT-SIZE: 12px;FONT-FAMILY: Arial Narrow;padding:2px 0 2px 0;">------------------ Original ------------------</div><div style="FONT-SIZE: 12px;background:#efefef;padding:8px;"><div id="menu_sender"><b>From: </b> "Zhang via llvm-dev"<llvm-dev@lists.llvm.org>;</div><div><b>Date: </b> Wed, Apr 17, 2019 04:35 AM</div><div><b>To: </b> "Viktor Was BSc"<gs15m015@technikum-wien.at>; "llvm-dev"<llvm-dev@lists.llvm.org>; <wbr></div><div></div><div><b>Subject: </b> Re: [llvm-dev] Opt plugin linkage</div></div><div> </div><div style="position:relative;"><div id="tmpcontent_res"></div><div>Hey:</div><div>I spent sometime debugging this, it seems like editing ``llvm/tools/opt.cpp`` and move ``cl::ParseCommandLineOptions(argc, argv,</div><div> "llvm .bc -> .bc modular optimizer and analysis printer\n");`` to the beginning of main() solved it for me. I'm not sure if this is a bug on LLVM side</div><div><br></div><div><br></div><div>Zhang</div><div><div> </div><div> </div><div style="font:Verdana normal 14px;color:#000;"><div style="FONT-SIZE: 12px;FONT-FAMILY: Arial Narrow;padding:2px 0 2px 0;">------------------ Original ------------------</div><div style="FONT-SIZE: 12px;background:#efefef;padding:8px;"><div id="menu_sender"><b>From: </b> "Viktor Was BSc via llvm-dev"<llvm-dev@lists.llvm.org>;</div><div><b>Date: </b> Wed, Apr 17, 2019 03:09 AM</div><div><b>To: </b> "llvm-dev"<llvm-dev@lists.llvm.org>; <wbr></div><div></div><div><b>Subject: </b> Re: [llvm-dev] Opt plugin linkage</div></div><div> </div><div style="position:relative;"><div id="tmpcontent_res"></div><div dir="auto">How come the hello pass example is so totally useless as a starting point? Why is this not using any library/compontent which could conflict with opt or clang and showing how to handle this? I have no clue as to how I have to setup llvm to get this to work or why it doesn't work in the first place with the setup described in "Getting started" and "writing an llvm pass" pages etc. <br></div>
<div dir="auto">Also there is basically no documentation for the custom cmake commands. <br><br></div>
<div dir="auto">Can please somebody help me with this issue? How do I get dynamically loaded llvm pass plugins to work? Am I the only one ever having this issue? <br><br></div>
<div dir="auto">Thanks <br></div>
<div dir="auto">Viktor </div>
<div class="gmail_quote">On Apr 16, 2019, at 05:38, Viktor Was BSc via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="auto">Hi,<br></div>
<div dir="auto">I have a dynamically loaded llvm pass built in-tree with ninja (generated with cmake, basically a copy of the hallo pass plugin, linux, llvm/clang version 6.0.1).<br></div>
<div dir="auto">It uses the ExecutionEngine.<br></div>
<div dir="auto">Building it without linking against LLVMExecutionEngine library results in an undefined symbol to the vtable of the EngineBuilder when loaded to opt. Linking the plugin with LLVMExecutionEngine results in the pass simply not being executable with giving "opt: Unkown command line argument '-passArg'." <br></div>
<div dir="auto">For a minimal example add set(LLVM_LINK_COMPONENTS Core) to the CMakeLists.txt of the Hello llvm pass. <br><br></div>
<div dir="auto">There is no error or warning at any point when linking or loading a plugin linked against some libs. <br></div>
<div dir="auto">How do I find out which llvm libs I can't link with a dynamically loaded plugin?<br></div>
<div dir="auto">How can I use the EngineBuilder in my plugin with proper symbol resolution?<br><br></div>
<div dir="auto">For reproductivity:<br></div>
<div dir="auto">cmake -G "Sublime Text 2 - Ninja" -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DLLVM_EXPORT_SYMBOLS_FOR_PLUGINS=ON -DLLVM_BUILD_TESTS=ON -DLLVM_BUILD_EXAMPLES=ON -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra" -DLLVM_TOOL_CLANG_BUILD=ON -DLLVM_TOOL_CLANG_TOOLS_EXTRA=ON -DLLVM_OPTIMIZED_TABLEGEN=ON -DCLANG_BUILD_EXAMPLES=ON -DCLANG_PLUGIN_SUPPORT=ON<br><br></div>
<div dir="auto">Hope someone can help me out.<br></div>
<div dir="auto">Viktor<br></div>
<pre class="blue"><hr><br>LLVM Developers mailing list<br>llvm-dev@lists.llvm.org<br><a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br></pre></blockquote></div>
</div></div></div></div></div><!--<![endif]--></includetail></div>