Peter Collingbourne 5f190b5e4e Introduce llvm::sys::getProcessTriple() function. ... In r143502, we renamed getHostTriple() to getDefaultTargetTriple() as part of work to allow the user to supply a different default target triple at configure time. This change also affected the JIT. However, it is inappropriate to use the default target triple in the JIT in most circumstances because this will not necessarily match the current architecture used by the process, leading to illegal instruction and other such errors at run time. Introduce the getProcessTriple() function for use in the JIT and its clients, and cause the JIT to use it. On architectures with a single bitness, the host and process triples are identical. On other architectures, the host triple represents the architecture of the host CPU, while the process triple represents the architecture used by the host CPU to interpret machine code within the current process. For example, when executing 32-bit code on a 64-bit Linux machine, the host triple may be 'x86_64-unknown-linux-gnu', while the process triple may be 'i386-unknown-linux-gnu'. This fixes JIT for the 32-on-64-bit (and vice versa) build on non-Apple platforms. Differential Revision: http://llvm-reviews.chandlerc.com/D254 llvm-svn: 172627		2013-01-16 17:27:22 +00:00
..
MCJIT	Introduce llvm::sys::getProcessTriple() function.	2013-01-16 17:27:22 +00:00
2002-12-16-ArgTest.ll	Some regression tests which are testing the old jit and are exercising functionality which is both known to be broken and not expected to be fixed in the old jit. To remove these from the regression test output, I've marked them XFAIL (for lit tests) and ifdef'd them out (unit tests). These modifications remove the last long-standing regression test failures from the buildbots (though updating the triple to reflect new ubuntu configuration has temporarily caused some new failures). Tested on x86-64 and ARM Linux.	2012-10-08 13:06:30 +00:00
2003-01-04-ArgumentBug.ll
2003-01-04-LoopTest.ll
2003-01-04-PhiTest.ll
2003-01-09-SARTest.ll
2003-01-10-FUCOM.ll
2003-01-15-AlignmentTest.ll
2003-05-06-LivenessClobber.ll
2003-05-07-ArgumentTest.ll
2003-05-11-PHIRegAllocBug.ll
2003-06-04-bzip2-bug.ll
2003-06-05-PHIBug.ll
2003-08-15-AllocaAssertion.ll
2003-08-21-EnvironmentTest.ll
2003-08-23-RegisterAllocatePhysReg.ll
2003-10-18-PHINode-ConstantExpr-CondCode-Failure.ll
2005-12-02-TailCallBug.ll
2007-12-10-APIntLoadStore.ll
2008-06-05-APInt-OverAShr.ll
2010-01-15-UndefValue.ll
fpbitcast.ll
hello2.ll
hello.ll
lit.local.cfg	Enable MCJIT tests on PowerPC.	2012-11-19 17:57:07 +00:00
simplesttest.ll
simpletest.ll
stubs.ll
test-arith.ll
test-branch.ll
test-call-no-external-funcs.ll
test-call.ll
test-cast.ll
test-common-symbols.ll
test-constantexpr.ll
test-fp-no-external-funcs.ll	Some regression tests which are testing the old jit and are exercising functionality which is both known to be broken and not expected to be fixed in the old jit. To remove these from the regression test output, I've marked them XFAIL (for lit tests) and ifdef'd them out (unit tests). These modifications remove the last long-standing regression test failures from the buildbots (though updating the triple to reflect new ubuntu configuration has temporarily caused some new failures). Tested on x86-64 and ARM Linux.	2012-10-08 13:06:30 +00:00
test-fp.ll	Some regression tests which are testing the old jit and are exercising functionality which is both known to be broken and not expected to be fixed in the old jit. To remove these from the regression test output, I've marked them XFAIL (for lit tests) and ifdef'd them out (unit tests). These modifications remove the last long-standing regression test failures from the buildbots (though updating the triple to reflect new ubuntu configuration has temporarily caused some new failures). Tested on x86-64 and ARM Linux.	2012-10-08 13:06:30 +00:00
test-global-init-nonzero.ll
test-global.ll
test-loadstore.ll
test-local.ll
test-logical.ll
test-loop.ll
test-phi.ll
test-ret.ll
test-return.ll
test-setcond-fp.ll
test-setcond-int.ll
test-shift.ll