Displaying 5 results from an estimated 5 matches for "eagermode".
2011 Nov 17
2
[LLVMdev] LLVM 3.0rc4 / 2.9: failing MultiJitTest.JitPool on Windows 7
...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
[ RUN ] MultiJitTest.EagerMode
[ OK ] MultiJitTest.EagerMode (10 ms)
[ RUN ] MultiJitTest.LazyMode
[ OK ] MultiJitTest.LazyMode (0 ms)
[ RUN ] MultiJitTest.JitPool
MultiJITTest.cpp:164: Failure
Value of: (intptr_t)&getPointerToNamedFunction
Actual: 4478936
Expected: (intptr_t)getPointerToNamed...
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
...nFunction
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., the JIT should not use the info from
the configure flag --host.)
Thanks,
Sebastian
>
> - Daniel
>
> O...
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
...::
> 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., the JIT should not use the info from
> the configure flag --host.)
Err, what? We can and...
2011 Jul 29
2
[LLVMdev] sys::getHostTriple failed to recognize ARM correctly
...ARM/ARMCodeEmitter.cpp:831!
0 libc.so.6 0x402e5000
Stack dump:
0. Running pass 'ARM Machine Code Emitter' on function '@recur1'
********************
Testing: 0 .. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90.
FAIL: LLVM-Unit :: ExecutionEngine/JIT/Debug+Asserts/JITTests/MultiJitTest.EagerMode (5875 of 6030)
******************** TEST 'LLVM-Unit :: ExecutionEngine/JIT/Debug+Asserts/JITTests/MultiJitTest.EagerMode' FAILED ********************
Note: Google Test filter = MultiJitTest.EagerMode
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up....
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
...onEngine/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., the JIT should not use the info from
>> the configure flag --host.)...