llvm-6502/lib/Support/Unix
Manuel Klimek b30614a1de Fix incorrectly finding 'executable' directories instead of files.
This broke for example the 'not' utility, if a directory called
'FileCheck' is executable and in the path before the actual 'FileCheck'.

This patch steals the implementation of the "old" PathV1 canExecute
implementation:
- checks for R_OK (file readable): this is necessary for executing
  scripts; we should not regress here unless we have good reasons
- checks for S_ISREG; if we want to get rid of this, we'd need to
  change all callers who already made the assumption when depending
  on Path V1.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@184074 91177308-0d34-0410-b5e6-96231b3b80d8
2013-06-17 10:48:34 +00:00
..
Host.inc
Memory.inc Remove declaration of __clear_cache for __APPLE__. <rdar://problem/13924072> 2013-05-19 20:33:51 +00:00
Mutex.inc
Path.inc Add GetCurrentDirectory back. 2013-06-14 21:41:33 +00:00
PathV2.inc Fix incorrectly finding 'executable' directories instead of files. 2013-06-17 10:48:34 +00:00
Process.inc
Program.inc Replace use of PathV1.h in Program.cpp. 2013-06-14 19:38:45 +00:00
README.txt
RWMutex.inc
Signals.inc Don't use PathV1.h in Signals.h. 2013-06-13 21:16:58 +00:00
system_error.inc
ThreadLocal.inc
TimeValue.inc
Unix.h
Watchdog.inc Add a new watchdog timer interface. The interface does not permit handling timeouts, so 2013-03-26 01:27:52 +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.