llvm-6502/lib/System/Unix
Reid Spencer 2a7d9e98ba For PR351:
Move the functionality of RunProgramWithTimeout into the ExecuteAndWait
function: support a timeout and I/O redirects


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@19043 91177308-0d34-0410-b5e6-96231b3b80d8
2004-12-19 18:00:44 +00:00
..
SUS Implementation of Process concept for SUSv2 platforms. 2004-09-11 04:54:06 +00:00
DynamicLibrary.cpp For PR351: 2004-12-19 18:00:32 +00:00
MappedFile.cpp Make the size() method const 2004-12-13 02:58:51 +00:00
MappedFile.inc Make the size() method const 2004-12-13 02:58:51 +00:00
Memory.cpp Provide a generic Unix implementation of the Memory concept. 2004-09-11 04:57:25 +00:00
Memory.inc Provide a generic Unix implementation of the Memory concept. 2004-09-11 04:57:25 +00:00
Path.cpp Change the signatures of the destroyFile and destroyDirectory methods to 2004-12-15 23:02:10 +00:00
Path.inc Change the signatures of the destroyFile and destroyDirectory methods to 2004-12-15 23:02:10 +00:00
Process.cpp Provide a generic unix implementation of the Process abstraction. 2004-09-11 04:56:56 +00:00
Process.inc Provide a generic unix implementation of the Process abstraction. 2004-09-11 04:56:56 +00:00
Program.cpp For PR351: 2004-12-19 18:00:44 +00:00
Program.inc For PR351: 2004-12-19 18:00:44 +00:00
README.txt Fix a typo. 2004-08-26 07:43:33 +00:00
Signals.cpp Path::get -> Path::toString 2004-12-11 00:14:15 +00:00
Signals.inc Path::get -> Path::toString 2004-12-11 00:14:15 +00:00
SysConfig.cpp Actually define PreventCoreFiles in the sys namespace. 2004-08-31 17:53:41 +00:00
TimeValue.cpp Per code review: 2004-11-16 06:22:17 +00:00
TimeValue.inc Per code review: 2004-11-16 06:22:17 +00:00
Unix.h Make this work with the ICC compiler, contributed by Bjørn Wennberg 2004-12-08 16:10:52 +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.