6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-11-11 23:05:31 +00:00
Code Issues Projects Releases Wiki Activity
93fa4766c2
llvm-6502/lib/Support/Unix
History
Argyrios Kyrtzidis 814450a429 Add an optional 'bool makeAbsolute' in llvm::sys::fs::unique_file function. 
If true and 'model' parameter is not an absolute path, a temp directory will be prepended.
Make it true by default to match current behaviour.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@136310 91177308-0d34-0410-b5e6-96231b3b80d8
2011-07-28 00:29:20 +00:00
..
Host.inc Don't include information about the build into the information returned by 2011-05-17 15:26:34 +00:00
Memory.inc setExecutable() should default to success if there's nothing custom for it. 2011-03-18 18:51:03 +00:00
Mutex.inc Now to chant the magical incantation that will exorcise the System library 2010-11-29 19:44:50 +00:00
Path.inc By default mkstemp() creates a temporary file with mode 0600, but the mode 2011-07-05 18:55:31 +00:00
PathV2.inc Add an optional 'bool makeAbsolute' in llvm::sys::fs::unique_file function. 2011-07-28 00:29:20 +00:00
Process.inc
Program.inc Have Program::Wait return -2 for crashed and timeouts instead of embedding 2011-05-21 00:56:46 +00:00
README.txt
RWMutex.inc Now to chant the magical incantation that will exorcise the System library 2010-11-29 19:44:50 +00:00
Signals.inc Include <pthread.h> before we use pthread_self/pthread_kill 2011-04-29 16:12:17 +00:00
system_error.inc Now to chant the magical incantation that will exorcise the System library 2010-11-29 19:44:50 +00:00
ThreadLocal.inc Now to chant the magical incantation that will exorcise the System library 2010-11-29 19:44:50 +00:00
TimeValue.inc
Unix.h Now to chant the magical incantation that will exorcise the System library 2010-11-29 19:44:50 +00:00

README.txt 

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