aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Reader/BitcodeReader.cpp
diff options
context:
space:
mode:
authorNico Weber <thakis@chromium.org>2021-01-27 08:52:23 -0500
committerNico Weber <thakis@chromium.org>2021-01-27 08:57:48 -0500
commit412ac0e53688364fe1295e864abd53e104eeb554 (patch)
treea25c01b946458b1559590ec6d9301f8fe9a74e7e /llvm/lib/Bitcode/Reader/BitcodeReader.cpp
parentd0e8a9e5a2f02ec1a3aa4c29469be504ff00d1db (diff)
downloadllvm-412ac0e53688364fe1295e864abd53e104eeb554.zip
llvm-412ac0e53688364fe1295e864abd53e104eeb554.tar.gz
llvm-412ac0e53688364fe1295e864abd53e104eeb554.tar.bz2
clang-cl: Prefer /vctoolsdir, /winsdkdir over LIB for link invocations
/vctoolsdir and /winsdkdir take precedence over the INCLUDE env var, so they should also take precedence over LIB. It's not quite as neat since LIB is still read by the linker and the linker just prefers the -libpath: paths the driver now passes, but as long as all libraries are present at /vctoolsdir and /winsdkdir, there's no harm in the linker also looking at LIB later. This fixes cl-options.c after a5d85cbe on Windows when LIB is set. Another way to fix the test would be to prefix the clang-cl line with `env --unset=LIB`, but I think it's better to fix the flag to work as expected instead of making the test work around the surprising behavior that LIB being set causes clang-cl to not pass -libpath: flags to the linker when /vctoolsdir and /winsdkdir are used.
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions