aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test
diff options
context:
space:
mode:
authorNico Weber <nicolasweber@gmx.de>2018-04-24 01:05:04 +0000
committerNico Weber <nicolasweber@gmx.de>2018-04-24 01:05:04 +0000
commita425db5a1e40c082a71bc23dcf8a57306d0e3ef0 (patch)
tree084f899ba642e18fd37c514dac36fae02a7cf308 /lldb/packages/Python/lldbsuite/test
parentd2a57220acfed8d910968435ca2d69ffe48117cc (diff)
downloadllvm-a425db5a1e40c082a71bc23dcf8a57306d0e3ef0.zip
llvm-a425db5a1e40c082a71bc23dcf8a57306d0e3ef0.tar.gz
llvm-a425db5a1e40c082a71bc23dcf8a57306d0e3ef0.tar.bz2
Remove code that's almost always dead, and harmful if not.
lit's util.which() would check if the passed-in path existed directly, and if so return it as-is. This is never the case when running llvm's, clang's, or lld's tests normally. But when running `./llvm-lit path/to/clang/test` with a cwd of llvm-build/bin, this if would detect that clang exists at path 'clang' and return 'clang' as the discovered clang binary -- and then lit would use the " clang " -> "*** Do not use 'clang' in tests, use '%clang'. ***" substitution to replace that with a broken test. By removing this early return, lit ends up with the usual absolute path and everything works even in this uncommon case. llvm-svn: 330672
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test')
0 files changed, 0 insertions, 0 deletions