projects / oota-llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 8f6a281) | patch
Revert r117582, which reverted r77396. Searching PATH for a string
authorDan Gohman <gohman@apple.com>
Thu, 28 Oct 2010 20:34:33 +0000 (20:34 +0000)
committerDan Gohman <gohman@apple.com>
Thu, 28 Oct 2010 20:34:33 +0000 (20:34 +0000)
commit24a492683ca02f234d727740f03c1fb2949f2b44
treeeb920f1dc7ae21df1872bace23efd7b0876a7c33tree | snapshot
parent8f6a281e979df1578526fc8a72a3c1bd33aa3efacommit | diff
Revert r117582, which reverted r77396. Searching PATH for a string
which contains slashes is inconsistent with the meaning of PATH on
Unix-type platforms, and pretty surprising.

If the user has given a specific path to execute and we can't
execute it, we should fail and say why.  (Apparently the new
posix_spawn code doesn't always say why, but that's a separate
issue.)

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@117596 91177308-0d34-0410-b5e6-96231b3b80d8
lib/System/Unix/Program.inc diff | blob | history
C/C++ LLVM-based compilers that forbids OOTA behaviors