search for: executionenginetest

...ols/clang/unittests/Basic/FileManagerTest.cpp:185:3: warning: passing NULL to non-pointer argument 3 of 'static testing::AssertionResult testing::internal::EqHelper<true>::Compare(const char*, const char*, const T1&, T2*) [with T1 = int, T2 = const clang::FileEntry]'" 2) ExecutionEngineTest "llvm[2]: Compiling ExecutionEngineTest.cpp for Debug+Asserts build C:/Programming/VersionControl/llvm/unittests/ExecutionEngine/ExecutionEngineTest.cpp: In member function 'virtual void<unnamed>::ExecutionEngineTest_ForwardGlobalMapping_Test::TestBody()': C:/Programming/Versi...

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) -lpthread -ldl The -lpthread -ldl is there explicitly because llvm-config prints them as part of --ldflags before the dependent LLVM libs. The first o...

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

...dule, which also uses the engine. See the small test case attached. Even if I bypass the dummy object and call LLVMLinkInJIT() directly, it still gets optimized out... ciao, Mario -------------- next part -------------- /* * vim: set tabstop=4 shiftwidth=4 expandtab: */ #define DEBUG_TYPE "ExecutionEngineTest" #include <llvm/ExecutionEngine/Interpreter.h> #include <llvm/ExecutionEngine/JIT.h> #include <llvm/Support/TargetSelect.h> #include <llvm/LLVMContext.h> #include <llvm/Module.h> #include <cassert> using namespace llvm; int main(void) { InitializeNat...

Hi, I have successfully built a shared version of LLVM (both 3.0rc4 and 2.9) on Windows 7 using MinGW. From there, I thought I would run the tests located under unittests (i.e. ADTTests, AnalysisTests, ExecutionEnginetests, JITTests, SupportTests, UtilsTests and VMCoreTests). All of them pass without any problem, except for JITTests which fails on the MultiJitTest.JitPool test: [==========] Running 25 tests from 6 test cases. [----------] Global test environment set-up. [----------] 3 tests from MultiJitTest...

2011/11/18 Alan Garny <alan.garny at dpag.ox.ac.uk>: > I have successfully built a shared version of LLVM (both 3.0rc4 and 2.9) on > Windows 7 using MinGW. From there, I thought I would run the tests located > under unittests (i.e. ADTTests, AnalysisTests, ExecutionEnginetests, > JITTests, SupportTests, UtilsTests and VMCoreTests). All of them pass > without any problem, except for JITTests which fails on the > MultiJitTest.JitPool test: > [ RUN      ] MultiJitTest.JitPool > > MultiJITTest.cpp:164: Failure > > Value of: (intptr_t)&getPointer...

...lbe; 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. 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) -lpthread -ldl The -lpthread -ldl is there explicitly because llvm-config prints them as part of --ldflags before the dependent LLVM libs. The first o...

Yeah, this is a problem with the static constructor getting optimized out. Including "JIT.h" is supposed to fix that. Is it possible that the file where you are including "JIT.h" doesn't have any required code in it? -Andy -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Mario Schwalbe Sent: Tuesday,

Hi, I'm on Linux and trying to link an application that makes use of LLVM's JIT execution engine statically. Setup: (1) LLVM libs are compiled as static libraries. (2) Called InitializeNativeTarget(). (3) Included llvm/ExecutionEngine/JIT.h. It works if I build and link regularly. However, if I add -static when linking, the execution engine fails to initialize. Does anyone know why?

...est.cpp for Release+Asserts build llvm[2]: Compiling MetadataTest.cpp for Release+Asserts build llvm[3]: ======= Finished Linking Release+Asserts Unit test MCJIT (without symbols) make[3]: Leaving directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/unittests/ExecutionEngine/MCJIT' llvm[2]: Compiling ExecutionEngineTest.cpp for Release+Asserts build llvm[2]: Compiling PointerIntPairTest.cpp for Release+Asserts build llvm[2]: ======= Finished Linking Release+Asserts Unit test MC (without symbols) make[2]: Leaving directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/unittests/MC' llvm[2]: Compiling PassManagerTest.cpp...

...FuzzMutate/CMakeFiles/FuzzMutateTests.dir 4.0K build/unittests/ExecutionEngine/Orc/CMakeFiles/OrcJITTests.dir 4.0K build/unittests/ExecutionEngine/MCJIT/CMakeFiles/MCJITTests.dir 4.0K build/unittests/ExecutionEngine/JITLink/CMakeFiles/JITLinkTests.dir 4.0K build/unittests/ExecutionEngine/CMakeFiles/ExecutionEngineTests.dir 4.0K build/unittests/Demangle/CMakeFiles/DemangleTests.dir 4.0K build/unittests/DebugInfo/PDB/CMakeFiles/DebugInfoPDBTests.dir 4.0K build/unittests/DebugInfo/MSF/CMakeFiles/DebugInfoMSFTests.dir 4.0K build/unittests/DebugInfo/DWARF/CMakeFiles/DebugInfoDWARFTests.dir 4.0K build/unittests/DebugI...