6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-12-23 15:29:51 +00:00
Code Issues Projects Releases Wiki Activity
0d1ea255d9
llvm-6502/lib/System/Unix
History
Owen Anderson 0d1ea255d9 Get rid of a helgrind warning. If this is _actually_ a performance problem, 
we can find a way to cache the answer that isn't racy.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@79472 91177308-0d34-0410-b5e6-96231b3b80d8
2009-08-19 21:48:34 +00:00
..
Alarm.inc Fix a bunch of namespace pollution. 2009-08-07 01:32:21 +00:00
Host.inc
Memory.inc Re-committing r76828 with the JIT memory manager changes now that the build 2009-07-23 21:46:56 +00:00
Mutex.inc Insert a SmartMutex templated class into the class hierarchy, which takes a template parameter specifying whether this mutex 2009-06-18 17:53:17 +00:00
Path.inc Minor code simplification. 2009-08-05 20:16:55 +00:00
Process.inc Get rid of a helgrind warning. If this is _actually_ a performance problem, 2009-08-19 21:48:34 +00:00
Program.inc Update a comment to reflect the current code. 2009-08-05 17:32:39 +00:00
README.txt
RWMutex.inc Give RWMutex the SmartRWMutex treatment too. 2009-06-18 18:26:15 +00:00
Signals.inc Add locking around signal handler registration. 2009-08-17 17:07:22 +00:00
ThreadLocal.inc Fix compilation without pthreads. 2009-06-26 08:48:03 +00:00
TimeValue.inc
Unix.h Add a portable strerror*() wrapper, llvm::sys::StrError(). This includes the 2009-07-01 18:11:20 +00:00

README.txt 

llvm/lib/System/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.