search for: livenessclobber

Displaying 15 results from an estimated 15 matches for "livenessclobber".

2013 Jun 10
0
[LLVMdev] EE/MCJIT XPASS on ARM
EE/JIT folks, When building release mode, 4 tests XPASS on ARM and I'm guessing is because they were relying on the assert being hit. Unexpected Passing Tests (4): LLVM :: ExecutionEngine/2003-05-06-LivenessClobber.ll LLVM :: ExecutionEngine/2003-08-15-AllocaAssertion.ll LLVM :: ExecutionEngine/2003-08-23-RegisterAllocatePhysReg.ll LLVM :: ExecutionEngine/MCJIT/test-global-init-nonzero-remote.ll Does anyone know what would be another way of testing this on Release mode? Shouldn't we also fail...
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
...I see the JIT cases failing: Failing Tests (26): LLVM :: ExecutionEngine/2002-12-16-ArgTest.ll LLVM :: ExecutionEngine/2003-01-04-ArgumentBug.ll LLVM :: ExecutionEngine/2003-01-04-LoopTest.ll LLVM :: ExecutionEngine/2003-01-15-AlignmentTest.ll LLVM :: ExecutionEngine/2003-05-06-LivenessClobber.ll LLVM :: ExecutionEngine/2003-05-07-ArgumentTest.ll LLVM :: ExecutionEngine/2003-06-04-bzip2-bug.ll LLVM :: ExecutionEngine/2003-08-15-AllocaAssertion.ll LLVM :: ExecutionEngine/2003-08-21-EnvironmentTest.ll LLVM :: ExecutionEngine/2003-08-23-RegisterAllocatePhysReg.ll LLV...
2012 Jun 19
2
[LLVMdev] mc jit
...003-01-04-LoopTest.ll LLVM :: ExecutionEngine/MCJIT/2003-01-04-PhiTest.ll LLVM :: ExecutionEngine/MCJIT/2003-01-09-SARTest.ll LLVM :: ExecutionEngine/MCJIT/2003-01-10-FUCOM.ll LLVM :: ExecutionEngine/MCJIT/2003-01-15-AlignmentTest.ll LLVM :: ExecutionEngine/MCJIT/2003-05-06-LivenessClobber.ll LLVM :: ExecutionEngine/MCJIT/2003-05-07-ArgumentTest.ll LLVM :: ExecutionEngine/MCJIT/2003-05-11-PHIRegAllocBug.ll LLVM :: ExecutionEngine/MCJIT/2003-06-04-bzip2-bug.ll LLVM :: ExecutionEngine/MCJIT/2003-06-05-PHIBug.ll LLVM :: ExecutionEngine/MCJIT/2003-08-15-AllocaAss...
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
...> > Failing Tests (26): >    LLVM :: ExecutionEngine/2002-12-16-ArgTest.ll >    LLVM :: ExecutionEngine/2003-01-04-ArgumentBug.ll >    LLVM :: ExecutionEngine/2003-01-04-LoopTest.ll >    LLVM :: ExecutionEngine/2003-01-15-AlignmentTest.ll >    LLVM :: ExecutionEngine/2003-05-06-LivenessClobber.ll >    LLVM :: ExecutionEngine/2003-05-07-ArgumentTest.ll >    LLVM :: ExecutionEngine/2003-06-04-bzip2-bug.ll >    LLVM :: ExecutionEngine/2003-08-15-AllocaAssertion.ll >    LLVM :: ExecutionEngine/2003-08-21-EnvironmentTest.ll >    LLVM :: ExecutionEngine/2003-08-23-RegisterAlloca...
2011 Jul 29
2
[LLVMdev] sys::getHostTriple failed to recognize ARM correctly
...'/nfs_home/chenwj/test/native-build/arm2/Debug+Asserts/bin/lli' '/nfs_home/chenwj/test/llvm/test/ExecutionEngine/2003-01-15-AlignmentTest.ll' > '/dev/null' -- ******************** Testing: 0 .. 10.. 20.. 30.. 40.. 50 FAIL: LLVM :: ExecutionEngine/2003-05-06-LivenessClobber.ll (3180 of 6030) ******************** TEST 'LLVM :: ExecutionEngine/2003-05-06-LivenessClobber.ll' FAILED ******************** Script: -- not /nfs_home/chenwj/test/native-build/arm2/Debug+Asserts/bin/lli /nfs_home/chenwj/test/llvm/test/ExecutionEngine/2003-05-06-LivenessClobber.ll -- Exit...
2013 Jun 05
0
[LLVMdev] More ExecutionEngine XPASS on ARM
I'm seeing more XPASSes on ExecutionEngine on ARM, but only on Release mode, not Release+Assert: $ grep XPASS final/logs/llvm.check-Phase3-Release.log XPASS: LLVM :: ExecutionEngine/2003-05-06-LivenessClobber.ll (10862 of 14500) XPASS: LLVM :: ExecutionEngine/2003-08-15-AllocaAssertion.ll (10868 of 14500) XPASS: LLVM :: ExecutionEngine/2003-08-23-RegisterAllocatePhysReg.ll (10870 of 14500) Any ideas why this is the case? cheers, --renato -------------- next part -------------- An HTML attachment was s...
2013 Dec 06
0
[LLVMdev] Disabling assertions fixes some XFAILs on ARMv7
Hi, This is true for release_34 and trunk. Disabling assertions makes the following tests pass: Unexpected Passing Tests (5): LLVM :: ExecutionEngine/2003-05-06-LivenessClobber.ll LLVM :: ExecutionEngine/2003-08-15-AllocaAssertion.ll LLVM :: ExecutionEngine/2003-08-23-RegisterAllocatePhysReg.ll LLVM :: ExecutionEngine/MCJIT/cross-module-sm-pic-a.ll LLVM :: ExecutionEngine/MCJIT/multi-module-sm-pic-a.ll -------------- next part -------------- An HTML attach...
2012 Jun 19
0
[LLVMdev] mc jit
On Mon, Jun 18, 2012 at 04:56:53PM -0700, reed kotler wrote: > I don't see any tests in either test or test-suite for -use-mcjit. For ARM, we need to manually switch to use mcjit, say $ make check-all LIT_ARGS=--param=jit_impl=mcjit Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799
2012 Jun 19
0
[LLVMdev] mc jit
...LLVM :: ExecutionEngine/MCJIT/2003-01-04-PhiTest.ll > LLVM :: ExecutionEngine/MCJIT/2003-01-09-SARTest.ll > LLVM :: ExecutionEngine/MCJIT/2003-01-10-FUCOM.ll > LLVM :: ExecutionEngine/MCJIT/2003-01-15-AlignmentTest.ll > LLVM :: ExecutionEngine/MCJIT/2003-05-06-LivenessClobber.ll > LLVM :: ExecutionEngine/MCJIT/2003-05-07-ArgumentTest.ll > LLVM :: ExecutionEngine/MCJIT/2003-05-11-PHIRegAllocBug.ll > LLVM :: ExecutionEngine/MCJIT/2003-06-04-bzip2-bug.ll > LLVM :: ExecutionEngine/MCJIT/2003-06-05-PHIBug.ll > LLVM :: ExecutionEng...
2012 Mar 27
0
[LLVMdev] [cfe-dev] Announcing 3.1 Release Branch Date!
Le mardi 27 mars 2012 à 14:36 -0700, Bill Wendling a écrit : > IMPORTANT! IMPORTANT! IMPORTANT! > [...] > By the way, we are looking for ARM testers. There was a lot of interest in the 3.0 release for an ARM release. We will try to do one this release on a trial basis. We are looking for ARMv7 cortex-a8 and cortex-a9 on Linux. If you are interested, I can upload the current trunk
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
...sts (26): >>    LLVM :: ExecutionEngine/2002-12-16-ArgTest.ll >>    LLVM :: ExecutionEngine/2003-01-04-ArgumentBug.ll >>    LLVM :: ExecutionEngine/2003-01-04-LoopTest.ll >>    LLVM :: ExecutionEngine/2003-01-15-AlignmentTest.ll >>    LLVM :: ExecutionEngine/2003-05-06-LivenessClobber.ll >>    LLVM :: ExecutionEngine/2003-05-07-ArgumentTest.ll >>    LLVM :: ExecutionEngine/2003-06-04-bzip2-bug.ll >>    LLVM :: ExecutionEngine/2003-08-15-AllocaAssertion.ll >>    LLVM :: ExecutionEngine/2003-08-21-EnvironmentTest.ll >>    LLVM :: ExecutionEngine/2003-...
2012 Jun 18
4
[LLVMdev] mc jit
I don't see any tests in either test or test-suite for -use-mcjit. Are we not testing this yet? There are lots of other llc options. What is our plan for testing these?
2012 Mar 27
5
[LLVMdev] Announcing 3.1 Release Branch Date!
IMPORTANT! IMPORTANT! IMPORTANT! We will be branching for the 3.1 release on April 16th! :-) This gives us a little over two weeks to get the trees into the most stable condition we can. What this means for you: All major features for the 3.1 release should be finished or near completion by the April 16th. After April 16th, we will accept only bug fixes and patches which do not change the
2011 Dec 15
2
[LLVMdev] llvm/clang test failures on powerpc-darwin8
...: ExecutionEngine/2003-01-04-LoopTest.ll LLVM : : ExecutionEngine/2003-01-04-PhiTest.ll LLVM : : ExecutionEngine/2003-01-09-SARTest.ll LLVM : : ExecutionEngine/2003-01-10-FUCOM.ll LLVM : : ExecutionEngine/2003-01-15-AlignmentTest.ll LLVM : : ExecutionEngine/2003-05-06-LivenessClobber.ll LLVM : : ExecutionEngine/2003-05-07-ArgumentTest.ll LLVM : : ExecutionEngine/2003-05-11-PHIRegAllocBug.ll LLVM : : ExecutionEngine/2003-06-04-bzip2-bug.ll LLVM : : ExecutionEngine/2003-06-05-PHIBug.ll LLVM : : ExecutionEngine/2003-08-15-AllocaAssertion.ll LLVM...
2009 Feb 23
1
[LLVMdev] 2.5 Pre-release2 available for testing
On Mon, Feb 23, 2009 at 12:12 AM, Aaron Gray < aaronngray.lists at googlemail.com> wrote: > On Sun, Feb 22, 2009 at 11:15 PM, Anton Korobeynikov < > anton at korobeynikov.info> wrote: > >> >> Actually its [configure-stage3-intl] where its hanging. >> >> This can easily be due to inline FP math in the stdlib headers. For >> example - I had to