summaryrefslogtreecommitdiffstats
path: root/llvm/lib/TextAPI/ELF/TBEHandler.cpp
diff options
context:
space:
mode:
authorBrian Gesiak <modocache@gmail.com>2018-12-10 00:56:13 +0000
committerBrian Gesiak <modocache@gmail.com>2018-12-10 00:56:13 +0000
commit5cc8920d02e90e1a5ec2e1a740f0c7f1bd87002f (patch)
tree96eadf67276a294034651f4695b55af4c30e9224 /llvm/lib/TextAPI/ELF/TBEHandler.cpp
parentdd5341f82d7be2480637c3ac99c443a62a37b499 (diff)
downloadbcm5719-llvm-5cc8920d02e90e1a5ec2e1a740f0c7f1bd87002f.tar.gz
bcm5719-llvm-5cc8920d02e90e1a5ec2e1a740f0c7f1bd87002f.zip
[bugpoint] Find 'opt', etc., in bugpoint directory
Summary: When bugpoint attempts to find the other executables it needs to run, such as `opt` or `clang`, it tries searching the user's PATH. However, in many cases, the 'bugpoint' executable is part of an LLVM build, and the 'opt' executable it's looking for is in that same directory. Many LLVM tools handle this case by using the `Paths` parameter of `llvm::sys::findProgramByName`, passing the parent path of the currently running executable. Do this same thing for bugpoint. However, to preserve the current behavior exactly, first search the user's PATH, and then search for 'opt' in the directory containing 'bugpoint'. Test Plan: `check-llvm`. Many of the existing bugpoint tests no longer need to use the `--opt-command` option as a result of these changes. Reviewers: MatzeB, silvas, davide Reviewed By: MatzeB, davide Subscribers: davide, llvm-commits Differential Revision: https://reviews.llvm.org/D54884 llvm-svn: 348734
Diffstat (limited to 'llvm/lib/TextAPI/ELF/TBEHandler.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud