1
0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-10-21 03:53:04 +02:00
llvm-mirror/lib/Support/Unix
Nick Lewycky d9c85b51b5 Teach Path::GetCurrentDirectory to use $PWD, to support users who like to do
screwy things by setting PWD != getcwd(). For example, some developers I know
will use this to control the value in gcc's DW_AT_comp_dir value in debug
output. With this patch, that trick will now work on clang too.

The only other effect of this change is that the static analysis will now
respect $PWD when reporting the directory of the files in its HTML output. I
think that's fine.

llvm-svn: 136459
2011-07-29 04:42:39 +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 Teach Path::GetCurrentDirectory to use $PWD, to support users who like to do 2011-07-29 04:42:39 +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

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.