summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Transforms/Utils/CodeExtractor.cpp
diff options
context:
space:
mode:
authorShoaib Meenai <smeenai@fb.com>2019-04-16 00:18:50 +0000
committerShoaib Meenai <smeenai@fb.com>2019-04-16 00:18:50 +0000
commit1826095a5faa4303c9fb5d3c5aadc46bf66c1cd6 (patch)
tree4544dcf818a516e53203e0a151a313193dacbc4c /llvm/lib/Transforms/Utils/CodeExtractor.cpp
parent0a61be96fc9f10f400497e98f5adb9cc467c98c6 (diff)
downloadbcm5719-llvm-1826095a5faa4303c9fb5d3c5aadc46bf66c1cd6.tar.gz
bcm5719-llvm-1826095a5faa4303c9fb5d3c5aadc46bf66c1cd6.zip
Reapply [Support] Fix recursive response file expansion guard
The test in the dependent revision has been fixed for Windows. Original commit message: Response file expansion limits the amount of expansion to prevent potential infinite recursion. However, the current logic assumes that any argument beginning with @ is a response file, which is not true for e.g. `-Xlinker -rpath -Xlinker @executable_path/../lib` on Darwin. Having too many of these non-response file arguments beginning with @ prevents actual response files from being expanded. Instead, limit based on the number of successful response file expansions, which should still prevent infinite recursion but also avoid false positives. Differential Revision: https://reviews.llvm.org/D60631 > llvm-svn: 358452 llvm-svn: 358466
Diffstat (limited to 'llvm/lib/Transforms/Utils/CodeExtractor.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud