6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-12-13 20:32:21 +00:00
Code Issues Projects Releases Wiki Activity
9a29cf281e
llvm-6502/lib/Support/Unix
History
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 <rdar://problem/13551789> Fix yet another race in unique_file. 2013-04-05 20:48:36 +00:00
Process.inc Workaround an MSan false positive. 2013-02-14 12:18:32 +00:00
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 Fix initialization-order bug in llvm::Support::TimeValue. TimeValue::now() is explicitly called during module initialization of lib/Support/Process.cpp. It reads the field of global object PosixZeroTime, which is not guaranteed to be initialized at this point. Found by AddressSanitizer with -fsanitize=init-order option. 2013-02-19 11:35:39 +00:00
Unix.h Sort includes for all of the .h files under the 'lib' tree. These were 2012-12-04 07:12:27 +00:00
Watchdog.inc Add a new watchdog timer interface. The interface does not permit handling timeouts, so 2013-03-26 01:27:52 +00:00

README.txt 

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.