search for: executionenginetests

Displaying 11 results from an estimated 11 matches for "executionenginetests".

Did you mean: executionenginetest
2011 Jul 23
2
[LLVMdev] Build of latest llvm gives warning and error
Building of llvm with gcc-4.5.2-1 gives these warnings: 1) Building FileManagerTest "llvm[4]: Compiling FileManagerTest.cpp for Debug+Asserts build C:/Programming/VersionControl/llvm/tools/clang/unittests/Basic/FileManagerTest.cpp: In member function 'virtual void<unnamed>::FileManagerTest_NoVirtualDirectoryExistsBeforeAVirtualFileIsAdded_Test::TestBody()':
2013 May 22
1
[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)
2013 May 22
0
[LLVMdev] Static linking of execution engine
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
2013 May 22
2
[LLVMdev] Static linking of execution engine
Hi, Am 21.05.13 21:57, schrieb Kaylor, Andrew: > 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? I'm including "JIT.h" directly in the main module, which also uses the engine. See
2011 Nov 17
2
[LLVMdev] LLVM 3.0rc4 / 2.9: failing MultiJitTest.JitPool on Windows 7
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 Nov 17
0
[LLVMdev] LLVM 3.0rc4 / 2.9: failing MultiJitTest.JitPool on Windows 7
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)&getPointerT...
2013 May 22
0
[LLVMdev] Static linking of execution engine
Hi Mario, It turns out that this isn't a problem with the static constructor at all. EngineBuilder::create() is calling dlopen (by way of sys::DynamicLibrary::loadLibraryPermanently) with a zero argument to get a handle the current module, which the default memory manager may later use for external symbol resolution. Because in your case the program is statically linked, the call to dlopen
2013 May 21
0
[LLVMdev] Static linking of execution engine
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,
2013 May 21
2
[LLVMdev] Static linking of execution engine
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?
2015 Jul 29
1
[LLVMdev] Error when i am using command make -j4 command in cygwin to compile safecode
llvm[4]: Compiling PoolAllocate.cpp for Release+Asserts build /home/NIKHILREDDY/WORK/LLVM_SRC/projects/poolalloc/lib/PoolAllocate/PoolAllocate.cpp: In member function ‘virtual bool llvm::PoolAllocate::runOnModule(llvm::Module&)’: /home/NIKHILREDDY/WORK/LLVM_SRC/projects/poolalloc/lib/PoolAllocate/PoolAllocate.cpp:403:16: error: ‘class llvm::Constant’ has no member named
2019 Apr 30
6
Disk space and RAM requirements in docs
...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/DebugIn...