Tim Northover e274b476de ARM: use pristine object file while processing relocations ... Previously we would read-modify-write the target bits when processing relocations for the MCJIT. This had the problem that when relocations were processed multiple times for the same object file (as they can be), the result is not idempotent and the values became corrupted. The solution to this is to take any bits used in the destination from the pristine object file as LLVM emitted it. This should fix PR16013 and remote MCJIT on ARM ELF targets. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@182800 91177308-0d34-0410-b5e6-96231b3b80d8		2013-05-28 19:48:19 +00:00
..
lit.local.cfg	Disable remote MCJIT on pre-v6 ARM	2013-05-20 07:46:06 +00:00
simpletest-remote.ll	ARM: use pristine object file while processing relocations	2013-05-28 19:48:19 +00:00
stubs-remote.ll	ARM: use pristine object file while processing relocations	2013-05-28 19:48:19 +00:00
test-common-symbols-remote.ll
test-data-align-remote.ll
test-fp-no-external-funcs-remote.ll	ARM: use pristine object file while processing relocations	2013-05-28 19:48:19 +00:00
test-global-init-nonzero-remote.ll
test-ptr-reloc-remote.ll