search for: lazyloadedjittest

Displaying 6 results from an estimated 6 matches for "lazyloadedjittest".

2011 Mar 28
1
[LLVMdev] [RC3] FreeBSD status.
...s_test.ll LLVM :: Feature/load_module.ll LLVM-Unit :: ExecutionEngine/JIT/Release/JITTests/JITTest.AvailableExternallyFunctionIsntCompiled LLVM-Unit :: ExecutionEngine/JIT/Release/JITTests/JITTest.AvailableExternallyGlobalIsntEmitted LLVM-Unit :: ExecutionEngine/JIT/Release/JITTests/LazyLoadedJITTest.MaterializableAvailableExternallyFunctionIsntCompiled Expected Passes : 8136 Expected Failures : 68 Unsupported Tests : 542 Unexpected Failures: 10 Following tests have failed because of -load command-line option: LLVM :: BugPoint/metadata.ll LLVM :: BugPoint/crash-narrowfunctiontest...
2011 Jul 29
2
[LLVMdev] sys::getHostTriple failed to recognize ARM correctly
...vm/lib/Target/ARM/ARMCodeEmitter.cpp:831! 0 libc.so.6 0x402e5000 Stack dump: 0. Running pass 'ARM Machine Code Emitter' on function '@func1' ******************** Testing: 0 .. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90. FAIL: LLVM-Unit :: ExecutionEngine/JIT/Debug+Asserts/JITTests/LazyLoadedJITTest.MaterializableAvailableExternallyFunctionIsntCompiled (5873 of 6030) ******************** TEST 'LLVM-Unit :: ExecutionEngine/JIT/Debug+Asserts/JITTests/LazyLoadedJITTest.MaterializableAvailableExternallyFunctionIsntCompiled' FAILED ******************** Note: Google Test filter = LazyLoadedJ...
2011 Sep 17
1
[LLVMdev] make check-all glitch cmake vs. configure on FreeBSD 8.2
...bleExternallyFunction' which could not be resolved! LLVM-Unit :: ExecutionEngine/JIT/Release/JITTests/JITTest.AvailableExternallyGlobalIsntEmitted LLVM ERROR: Could not resolve external global address: JITTest_AvailableExternallyGlobal LLVM-Unit :: ExecutionEngine/JIT/Release/JITTests/LazyLoadedJITTest.MaterializableAvailableExternallyFunctionIsntCompiled LLVM ERROR: Program used external function 'JITTest_AvailableExternallyFunction' which could not be resolved!
2011 Nov 04
7
[LLVMdev] JIT should query host info at runtime - Re: buildbot failure in LLVM on llvm-gcc-build-x86_64-darwin10-x-mingw32-x-armeabi
...ITTests/JITTest.EscapedLazyStubStillCallable LLVM-Unit :: ExecutionEngine/JIT/Debug+Asserts/JITTests/JITTest.FarCallToKnownFunction LLVM-Unit :: ExecutionEngine/JIT/Debug+Asserts/JITTests/JITTest.FunctionPointersOutliveTheirCreator LLVM-Unit :: ExecutionEngine/JIT/Debug+Asserts/JITTests/LazyLoadedJITTest.EagerCompiledRecursionThroughGhost LLVM-Unit :: ExecutionEngine/JIT/Debug+Asserts/JITTests/MultiJitTest.EagerMode LLVM-Unit :: ExecutionEngine/JIT/Debug+Asserts/JITTests/MultiJitTest.LazyMode I think that for JIT, the compiler should figure out what the host is with a *runtime* check (i.e....
2011 Nov 04
0
[LLVMdev] JIT should query host info at runtime - Re: buildbot failure in LLVM on llvm-gcc-build-x86_64-darwin10-x-mingw32-x-armeabi
...StubStillCallable >    LLVM-Unit :: > ExecutionEngine/JIT/Debug+Asserts/JITTests/JITTest.FarCallToKnownFunction >    LLVM-Unit :: > ExecutionEngine/JIT/Debug+Asserts/JITTests/JITTest.FunctionPointersOutliveTheirCreator >    LLVM-Unit :: > ExecutionEngine/JIT/Debug+Asserts/JITTests/LazyLoadedJITTest.EagerCompiledRecursionThroughGhost >    LLVM-Unit :: > ExecutionEngine/JIT/Debug+Asserts/JITTests/MultiJitTest.EagerMode >    LLVM-Unit :: > ExecutionEngine/JIT/Debug+Asserts/JITTests/MultiJitTest.LazyMode > > I think that for JIT, the compiler should figure out what the host >...
2011 Nov 04
1
[LLVMdev] JIT should query host info at runtime - Re: buildbot failure in LLVM on llvm-gcc-build-x86_64-darwin10-x-mingw32-x-armeabi
...t;    LLVM-Unit :: >> ExecutionEngine/JIT/Debug+Asserts/JITTests/JITTest.FarCallToKnownFunction >>    LLVM-Unit :: >> ExecutionEngine/JIT/Debug+Asserts/JITTests/JITTest.FunctionPointersOutliveTheirCreator >>    LLVM-Unit :: >> ExecutionEngine/JIT/Debug+Asserts/JITTests/LazyLoadedJITTest.EagerCompiledRecursionThroughGhost >>    LLVM-Unit :: >> ExecutionEngine/JIT/Debug+Asserts/JITTests/MultiJitTest.EagerMode >>    LLVM-Unit :: >> ExecutionEngine/JIT/Debug+Asserts/JITTests/MultiJitTest.LazyMode >> >> I think that for JIT, the compiler should figur...