summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Support/Unix
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2012-01-15 08:41:35 +0000
committerChandler Carruth <chandlerc@gmail.com>2012-01-15 08:41:35 +0000
commitda22f30e721f1ce3ffc51ead2b06910b436a7d2e (patch)
tree7a65dc8f674c7ab3d39fe952c2b0540bab517850 /llvm/lib/Support/Unix
parentbd1530949d568ad5da39b9d33adef8a5d0552961 (diff)
downloadbcm5719-llvm-da22f30e721f1ce3ffc51ead2b06910b436a7d2e.tar.gz
bcm5719-llvm-da22f30e721f1ce3ffc51ead2b06910b436a7d2e.zip
Remove SetWorkingDirectory from the Process interface. Nothing in LLVM
or Clang is using this, and it would be hard to use it correctly given the thread hostility of the function. Also, it never checked the return which is rather dangerous with chdir. If someone was in fact using this, please let me know, as well as what the usecase actually is so that I can add it back and make it more correct and secure to use. (That said, it's never going to be "safe" per-se, but we could at least document the risks...) llvm-svn: 148211
Diffstat (limited to 'llvm/lib/Support/Unix')
-rw-r--r--llvm/lib/Support/Unix/Process.inc4
1 files changed, 0 insertions, 4 deletions
diff --git a/llvm/lib/Support/Unix/Process.inc b/llvm/lib/Support/Unix/Process.inc
index da440fd48f3..5cdb11ccebc 100644
--- a/llvm/lib/Support/Unix/Process.inc
+++ b/llvm/lib/Support/Unix/Process.inc
@@ -293,7 +293,3 @@ const char *Process::OutputBold(bool bg) {
const char *Process::ResetColor() {
return "\033[0m";
}
-
-void Process::SetWorkingDirectory(std::string Path) {
- ::chdir(Path.c_str());
-}
OpenPOWER on IntegriCloud