summaryrefslogtreecommitdiffstats
path: root/llvm/lib/CodeGen/SafeStackColoring.cpp
diff options
context:
space:
mode:
authorJoel E. Denny <jdenny.ornl@gmail.com>2019-11-01 10:14:22 -0400
committerJoel E. Denny <jdenny.ornl@gmail.com>2019-11-01 14:08:52 -0400
commitcb2c4bb0e0da675bb0ab3a3fce4cbb014d83f675 (patch)
treea077556dedc17a1e421773b5285fd8ac429d5546 /llvm/lib/CodeGen/SafeStackColoring.cpp
parent45ee0d6de6f82833de1320de35366669b2b1cdf2 (diff)
downloadbcm5719-llvm-cb2c4bb0e0da675bb0ab3a3fce4cbb014d83f675.tar.gz
bcm5719-llvm-cb2c4bb0e0da675bb0ab3a3fce4cbb014d83f675.zip
[lit] Fix internal env calling env
Without this patch, when using lit's internal shell, if `env` on a lit RUN line calls `env`, lit accidentally searches for the latter as an external executable. What's worse is that works fine when a developer is testing on a platform where `env` is available and behaves as expected, but it then breaks on other platforms. `env` calling `env` can make sense if one such `env` is within a lit substitution, as in D65156 and D65121. This patch ensures that lit executes both as internal commands. Reviewed By: probinson, mgorny, rnk Differential Revision: https://reviews.llvm.org/D65697
Diffstat (limited to 'llvm/lib/CodeGen/SafeStackColoring.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud