llvm-6502/lib/System/Unix
Reid Kleckner 10b4fc552f Re-committing r76828 with the JIT memory manager changes now that the build
bots like the BumpPtrAllocator changes.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@76902 91177308-0d34-0410-b5e6-96231b3b80d8
2009-07-23 21:46:56 +00:00
..
Alarm.inc Add a Sleep() function. 2009-02-08 22:47:39 +00:00
Host.inc Add llvm::sys::getHostTriple and remove 2009-03-31 17:30:15 +00:00
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 Improve sys::Path::makeAbsolute on Win32. 2009-07-12 20:23:56 +00:00
Process.inc Add support for outputting ANSI colors to raw_fd_ostream. 2009-06-04 07:09:50 +00:00
Program.inc Remove duplication in Program::Execute{And,No}Wait. 2009-07-18 21:43:12 +00:00
README.txt Fix a typo. 2004-08-26 07:43:33 +00:00
RWMutex.inc Give RWMutex the SmartRWMutex treatment too. 2009-06-18 18:26:15 +00:00
Signals.inc fix PR3965:SIGINT handler not restored after calling ParseAST(), 2009-04-12 23:33:13 +00:00
ThreadLocal.inc Fix compilation without pthreads. 2009-06-26 08:48:03 +00:00
TimeValue.inc Remove attribution from file headers, per discussion on llvmdev. 2007-12-29 20:36:04 +00:00
Unix.h Add a portable strerror*() wrapper, llvm::sys::StrError(). This includes the 2009-07-01 18:11:20 +00:00

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.