summaryrefslogtreecommitdiff
path: root/lib/Support/Unix
diff options
context:
space:
mode:
authorTim Northover <Tim.Northover@arm.com>2013-05-04 18:52:44 +0000
committerTim Northover <Tim.Northover@arm.com>2013-05-04 18:52:44 +0000
commit9a29cf281e5fc4e3fd4f4f83296fbc22ebfdac86 (patch)
tree66201d91ab9ac99e66d88fb2d0e11370621449c2 /lib/Support/Unix
parent7153a30610e78c5cd1347a31f3a90dde2f335f37 (diff)
downloadllvm-9a29cf281e5fc4e3fd4f4f83296fbc22ebfdac86.tar.gz
llvm-9a29cf281e5fc4e3fd4f4f83296fbc22ebfdac86.tar.bz2
llvm-9a29cf281e5fc4e3fd4f4f83296fbc22ebfdac86.tar.xz
AArch64: use __clear_cache under GCCish environments
AArch64 is going to need some kind of cache-invalidation in order to successfully JIT since it has a weak memory-model. This is provided by a __clear_cache builtin in libgcc, which acts very much like the 32-bit ARM equivalent (on platforms where it exists). git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181129 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/Support/Unix')
-rw-r--r--lib/Support/Unix/Memory.inc2
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/Support/Unix/Memory.inc b/lib/Support/Unix/Memory.inc
index e9b26bdb80..72a8af621d 100644
--- a/lib/Support/Unix/Memory.inc
+++ b/lib/Support/Unix/Memory.inc
@@ -325,7 +325,7 @@ void Memory::InvalidateInstructionCache(const void *Addr,
for (intptr_t Line = StartLine; Line < EndLine; Line += LineSize)
asm volatile("icbi 0, %0" : : "r"(Line));
asm volatile("isync");
-# elif defined(__arm__) && defined(__GNUC__)
+# elif (defined(__arm__) || defined(__aarch64__)) && defined(__GNUC__)
// FIXME: Can we safely always call this for __GNUC__ everywhere?
const char *Start = static_cast<const char *>(Addr);
const char *End = Start + Len;