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
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@172627 91177308-0d34-0410-b5e6-96231b3b80d8
2013-01-16 17:27:22 +00:00
|
|
|
; RUN: %lli_mcjit %s > /dev/null
|
2012-05-17 21:07:47 +00:00
|
|
|
|
|
|
|
|
; Testcase distilled from 256.bzip2.
|
|
|
|
|
|
|
|
|
|
target datalayout = "e-p:32:32"
|
|
|
|
|
|
|
|
|
|
define i32 @main() {
|
|
|
|
|
entry:
|
|
|
|
|
%X = add i32 1, -1 ; <i32> [#uses=3]
|
|
|
|
|
br label %Next
|
|
|
|
|
Next: ; preds = %entry
|
|
|
|
|
%A = phi i32 [ %X, %entry ] ; <i32> [#uses=0]
|
|
|
|
|
%B = phi i32 [ %X, %entry ] ; <i32> [#uses=0]
|
|
|
|
|
%C = phi i32 [ %X, %entry ] ; <i32> [#uses=1]
|
|
|
|
|
ret i32 %C
|
|
|
|
|
}
|
|
|
|
|
|
