llvm-6502/lib/Support/Unix
Sylvestre Ledru bec3ce0cb5 The assumption that /proc/self/exe always exists is incorrect.
For example, under a Linux chroot, /proc/ might not be mounted.
Therefor, we test if this file exist. If it is the case, use it (the current
behavior). Otherwise, we fall back to the detection used by *BSD.

The issue has been reported initially on the Debian bug tracker:
http://bugs.debian.org/674588



git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@164676 91177308-0d34-0410-b5e6-96231b3b80d8
2012-09-26 08:30:35 +00:00
..
Host.inc revert r147542 after comments from Joerg Sonnenberger 2012-01-05 18:28:46 +00:00
Memory.inc This patch adds memory support functions which will later be used to implement section-specific protection handling in MCJIT. 2012-09-19 20:46:12 +00:00
Mutex.inc
Path.inc The assumption that /proc/self/exe always exists is incorrect. 2012-09-26 08:30:35 +00:00
PathV2.inc Properly test the LLVM_USE_RVALUE_REFERENCES macro. 2012-08-15 19:16:27 +00:00
Process.inc Add support for the OpenBSD for Bitrig. 2012-08-06 20:52:18 +00:00
Program.inc Support/Program: Make Change<stream>ToBinary return error_code. 2011-12-13 23:16:49 +00:00
README.txt
RWMutex.inc
Signals.inc Add an --enable-backtraces option to configure to determine 2012-09-21 23:03:29 +00:00
system_error.inc
ThreadLocal.inc
TimeValue.inc
Unix.h [Support/Unix] Unconditionally include time.h. 2012-04-23 19:00:27 +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.