6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-12-14 11:32:34 +00:00
Code Issues Projects Releases Wiki Activity
c33e4930d4
llvm-6502/lib/System/Unix
History
Reid Spencer d0ae93f022 For PR351: 
SysConf abstraction was pointless because it had a single function in it that
pertained only to the current process. So merge it into the Process abstraction
and remove the files completely.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@19149 91177308-0d34-0410-b5e6-96231b3b80d8
2004-12-27 06:15:14 +00:00
..
SUS Implementation of Process concept for SUSv2 platforms. 2004-09-11 04:54:06 +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 For PR351: 2004-12-24 06:29:42 +00:00
Path.inc For PR351: 2004-12-24 06:29:42 +00:00
Process.cpp Implement GetTimeUsage correctly. 2004-12-20 21:43:33 +00:00
Process.inc Implement GetTimeUsage correctly. 2004-12-20 21:43:33 +00:00
Program.cpp Make references to 'struct sigaction' compile under Solaris. 2004-12-19 18:58:11 +00:00
Program.inc Make references to 'struct sigaction' compile under Solaris. 2004-12-19 18:58:11 +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
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

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.