search for: m3o

...LLVM code, you can also work around this problem by using ExecutionEngine::createJIT(), which does not make the dlopen check. I suspect that code path is not well tested, so there may be additional problems if you do things that way. -Andy -----Original Message----- From: Mario Schwalbe [mailto:m3o.s6e at googlemail.com] Sent: Wednesday, May 22, 2013 11:30 AM To: Kaylor, Andrew Cc: Mario Schwalbe; LLVM Devel Subject: Re: [LLVMdev] Static linking of execution engine Am 22.05.13 19:32, schrieb Kaylor, Andrew: > If you send me details about how you're building this I'll look into it...

Am 22.05.13 19:32, schrieb Kaylor, Andrew: > If you send me details about how you're building this I'll look into it. Thanks. I forgot to mention it's LLVM 3.2 on Ubuntu 12.10. The command line is: $ g++-4.7 ExecutionEngineTest.cpp $(llvm-config --cxxflags --ldflags --libs) -lpthread -ldl $ g++-4.7 -static ExecutionEngineTest.cpp $(llvm-config --cxxflags --ldflags --libs)

If you send me details about how you're building this I'll look into it. -Andy -----Original Message----- From: Mario Schwalbe [mailto:mario at se.inf.tu-dresden.de] Sent: Wednesday, May 22, 2013 2:34 AM To: Kaylor, Andrew Cc: Mario Schwalbe; LLVM Devel Subject: Re: [LLVMdev] Static linking of execution engine Hi, Am 21.05.13 21:57, schrieb Kaylor, Andrew: > Yeah, this is a problem

Hi, I can confirm this problem. We use clang's libtooling ToolInvocation object and the second module fails to compile even through it's a completely fresh instance. Adding -fno-vectorize explicitly seems to work around this problem, but does anyone know a real fix? ciao, Mario Am 20.06.13 15:07, schrieb Alan Garny: > My application generates some C code which I then compile using

Hi, My application generates some C code which I then compile using LLVM+Clang before running it. For the compilation side of things, I have a class which one of the methods (the CompilerEngine::compileCode() method in https://raw.github.com/opencor/opencor/llvm_3.3/src/plugins/misc/Compiler/sr c/compilerengine.cpp) is based on the code from the clang-interpreter example

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking