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?
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 #1667 Homepage: http://people.cs.nctu.edu.tw/~chenwj
On 06/18/2012 07:21 PM, 陳韋任 (Wei-Ren Chen) wrote:> make check-all LIT_ARGS=--param=jit_impl=mcjitThanks. When I run this on x86 ubuntu, there are 47 failures. Failing Tests (47): LLVM :: ExecutionEngine/MCJIT/2002-12-16-ArgTest.ll LLVM :: ExecutionEngine/MCJIT/2003-01-04-ArgumentBug.ll LLVM :: ExecutionEngine/MCJIT/2003-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-AllocaAssertion.ll LLVM :: ExecutionEngine/MCJIT/2003-08-21-EnvironmentTest.ll LLVM :: ExecutionEngine/MCJIT/2003-08-23-RegisterAllocatePhysReg.ll LLVM :: ExecutionEngine/MCJIT/2003-10-18-PHINode-ConstantExpr-CondCode-Failure.ll LLVM :: ExecutionEngine/MCJIT/2005-12-02-TailCallBug.ll LLVM :: ExecutionEngine/MCJIT/2007-12-10-APIntLoadStore.ll LLVM :: ExecutionEngine/MCJIT/2008-06-05-APInt-OverAShr.ll LLVM :: ExecutionEngine/MCJIT/2010-01-15-UndefValue.ll LLVM :: ExecutionEngine/MCJIT/fpbitcast.ll LLVM :: ExecutionEngine/MCJIT/hello.ll LLVM :: ExecutionEngine/MCJIT/hello2.ll LLVM :: ExecutionEngine/MCJIT/simplesttest.ll LLVM :: ExecutionEngine/MCJIT/simpletest.ll LLVM :: ExecutionEngine/MCJIT/stubs.ll LLVM :: ExecutionEngine/MCJIT/test-arith.ll LLVM :: ExecutionEngine/MCJIT/test-branch.ll LLVM :: ExecutionEngine/MCJIT/test-call-no-external-funcs.ll LLVM :: ExecutionEngine/MCJIT/test-call.ll LLVM :: ExecutionEngine/MCJIT/test-cast.ll LLVM :: ExecutionEngine/MCJIT/test-common-symbols.ll LLVM :: ExecutionEngine/MCJIT/test-constantexpr.ll LLVM :: ExecutionEngine/MCJIT/test-fp-no-external-funcs.ll LLVM :: ExecutionEngine/MCJIT/test-fp.ll LLVM :: ExecutionEngine/MCJIT/test-global-init-nonzero.ll LLVM :: ExecutionEngine/MCJIT/test-global.ll LLVM :: ExecutionEngine/MCJIT/test-loadstore.ll LLVM :: ExecutionEngine/MCJIT/test-local.ll LLVM :: ExecutionEngine/MCJIT/test-logical.ll LLVM :: ExecutionEngine/MCJIT/test-loop.ll LLVM :: ExecutionEngine/MCJIT/test-phi.ll LLVM :: ExecutionEngine/MCJIT/test-ret.ll LLVM :: ExecutionEngine/MCJIT/test-return.ll LLVM :: ExecutionEngine/MCJIT/test-setcond-fp.ll LLVM :: ExecutionEngine/MCJIT/test-setcond-int.ll LLVM :: ExecutionEngine/MCJIT/test-shift.ll Expected Passes : 10774 Expected Failures : 82 Unsupported Tests : 14 Unexpected Failures: 47
> -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of reed kotler > Sent: Tuesday, June 19, 2012 02:57 > To: ll >> "llvmdev at cs.uiuc.edu" > Subject: [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? >test/ExecutionEngine/MCJIT is currently a duplicate of test/ExecutionEngine, which runs the tests with MCJIT. So it already runs every time you "make check" (on build-bots too!). The duplication is unfortunate, but hopefully temporary - once the LIT SUBTEST patch gets in (it's been in review for ages now, ahem ;-) ) it should be gone and each test in test/ExecutionEngine will just be run twice - with old JIT and MCJIT. Eli --------------------------------------------------------------------- Intel Israel (74) Limited This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
> test/ExecutionEngine/MCJIT is currently a duplicate of test/ExecutionEngine, which runs the tests with MCJIT. So it already runs every time you "make check" (on build-bots too!). The duplication is unfortunate, but hopefully temporary - once the LIT SUBTEST patch gets in (it's been in review for ages now, ahem ;-) ) it should be gone and each test in test/ExecutionEngine will just be run twice - with old JIT and MCJIT.When I tested ARM before LLVM 3.1 released, I was told that mcjit is enabled by default on x86, on ARM I need to switch to mcjit manaully. Is that right? I am confused here. :) Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667 Homepage: http://people.cs.nctu.edu.tw/~chenwj