6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-08-24 09:29:42 +00:00
Code Issues Projects Releases Wiki Activity
389f13012f
llvm-6502/lib/Support/Unix
History
Dylan Noblesmith 389f13012f Support: add llvm::unique_lock 
Based on the STL class of the same name, it guards a mutex
while also allowing it to be unlocked conditionally before
destruction.

This eliminates the last naked usages of mutexes in LLVM and
clang.

It also uncovered and fixed a bug in callExternalFunction()
when compiled without USE_LIBFFI, where the mutex would never
be unlocked if the end of the function was reached.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@216338 91177308-0d34-0410-b5e6-96231b3b80d8
2014-08-23 23:07:14 +00:00
..
Host.inc Support: normalize the default triple on Unix 2014-03-30 03:22:37 +00:00
Memory.inc Revert: r211588 - [mips] Use __clear_cache builtin instead of cacheflush() in Unix Memory::InvalidateInstructionCache() 2014-06-24 13:53:56 +00:00
Mutex.inc
Path.inc Remove dead code. Fixes pr20544. 2014-08-08 21:35:52 +00:00
Process.inc Remove 'using std::errro_code' from lib. 2014-06-13 02:24:39 +00:00
Program.inc lldb can interrupt waitpid, so EINTR shouldn't be an error. This fixes the case 2014-06-27 18:02:54 +00:00
README.txt
RWMutex.inc Fix RWMutex to be thread-safe when pthread_rwlock is not available 2014-03-01 04:30:32 +00:00
Signals.inc Support: add llvm::unique_lock 2014-08-23 23:07:14 +00:00
ThreadLocal.inc Make sys::ThreadLocal<> zero-initialized on non-thread builds (PR18205) 2013-12-19 20:32:44 +00:00
TimeValue.inc [C++] Use 'nullptr'. 2014-04-28 04:05:08 +00:00
Unix.h Canonicalize header guards into a common format. 2014-08-13 16:26:38 +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.