Thanks all for replying! I'll try the CostModel class first. Jingyue On Thu, Jan 15, 2015 at 3:47 AM, Jonas Wagner <jonas.wagner at epfl.ch> wrote:> Hi, > > 3. CostModel::getInstructionCost::getInstructionCost in >> lib/Analysis/CostModel.cpp >> > > I've been using the CostModel class in a project, and it has worked quite > well. I don't have very high requirements on precision, though. > > Note that in order to use it, you'll probably have to create a public > header file for the class. This thread here has some more details on this: > http://lists.cs.uiuc.edu/pipermail/llvmdev/2014-July/thread.html#74836 > > Cheers, > Jonas >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150120/4148cfa1/attachment.html>
Hi, I'm using the code of the tool "lli" embedded in a process of a controll application. After the second JIT compile action I see the following messages: first JIT compile .. with a dump of the actual parameters: xargv: -load xargv: libqwt.so xargv: -load xargv: libosz.so xargv: -entry-function=main xargv: -use-mcjit xargv: source.bc -> the jitted application code works ! second JIT compile: xargv: -load xargv: libqwt.so xargv: -load xargv: libosz.so xargv: -entry-function=main xargv: -use-mcjit xargv: source.bc dV: for the -entry-function option: may only occur zero or one times! dV: for the -use-mcjit option: may only occur zero or one times! <input bitcode> option: may only occur zero or one times! The execution engine is deleted after the first JIT action ... but it seems not to be sufficient in order to run multiple JIT compiles. What's to do additionally to reset (or re-initialize) lli ? Regards Armin
Hi Armin, Argument parsing isn't handled by the JIT. This sounds like you're making redundant calls to cl::ParseCommandLineOptions ? Deleting the ExecutionEngine and any RTDyldMemoryManager instances that you've created should be enough to reset the JIT. Cheers, Lang. On Tue, Jan 20, 2015 at 12:38 PM, Armin Steinhoff <armin at steinhoff.de> wrote:> > Hi, > > I'm using the code of the tool "lli" embedded in a process of a controll > application. > > After the second JIT compile action I see the following messages: > > first JIT compile .. with a dump of the actual parameters: > > xargv: -load > xargv: libqwt.so > xargv: -load > xargv: libosz.so > xargv: -entry-function=main > xargv: -use-mcjit > xargv: source.bc -> the jitted application code works ! > > second JIT compile: > > xargv: -load > xargv: libqwt.so > xargv: -load > xargv: libosz.so > xargv: -entry-function=main > xargv: -use-mcjit > xargv: source.bc > dV: for the -entry-function option: may only occur zero or one times! > dV: for the -use-mcjit option: may only occur zero or one times! > <input bitcode> option: may only occur zero or one times! > > The execution engine is deleted after the first JIT action ... but it > seems not to be sufficient in order to run multiple JIT compiles. > > What's to do additionally to reset (or re-initialize) lli ? > > Regards > > Armin > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150120/765f8979/attachment.html>