6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-11-16 11:05:54 +00:00
Code Issues Projects Releases Wiki Activity
66f1b378bc
llvm-6502/lib/System/Unix
History
Daniel Dunbar a00e85c9b1 Improve sys::Path::makeAbsolute on Win32. 
- Patch by Viktor Kutuzov!

 - Minor tweak by me to add llvm_unreachable calls on FIXMEd error paths.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@75424 91177308-0d34-0410-b5e6-96231b3b80d8
2009-07-12 20:23:56 +00:00
..
Alarm.inc
Host.inc
Memory.inc Make Unix.h:MakeErrMsg separate the prefix and errno string, so we get: 2009-04-20 20:50:13 +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 Add an ExecuteNoWait interface to support asynchronous process spawning. 2009-07-08 21:46:40 +00:00
README.txt
RWMutex.inc Give RWMutex the SmartRWMutex treatment too. 2009-06-18 18:26:15 +00:00
Signals.inc
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.