llvm-6502/lib/Support/Unix
Tim Northover 9a29cf281e 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
2013-05-04 18:52:44 +00:00
..
Host.inc
Memory.inc AArch64: use __clear_cache under GCCish environments 2013-05-04 18:52:44 +00:00
Mutex.inc
Path.inc
PathV2.inc
Process.inc
Program.inc Add a function to check if an argument list is too long. 2013-04-11 14:06:34 +00:00
README.txt
RWMutex.inc
Signals.inc [SystemZ] Support System Z as host architecture 2013-05-03 12:22:11 +00:00
system_error.inc
ThreadLocal.inc
TimeValue.inc
Unix.h
Watchdog.inc

llvm/lib/Support/Unix README
===========================

This directory provides implementations of the lib/System classes that
are common to two or more variants of UNIX. For example, the directory
structure underneath this directory could look like this:

Unix           - only code that is truly generic to all UNIX platforms
  Posix        - code that is specific to Posix variants of UNIX
  SUS          - code that is specific to the Single Unix Specification
  SysV         - code that is specific to System V variants of UNIX

As a rule, only those directories actually needing to be created should be
created. Also, further subdirectories could be created to reflect versions of
the various standards. For example, under SUS there could be v1, v2, and v3
subdirectories to reflect the three major versions of SUS.