aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/CodeGen/CodeGenFunction.cpp
diff options
context:
space:
mode:
authorJez Ng <jezng@fb.com>2021-10-21 11:23:34 -0400
committerJez Ng <jezng@fb.com>2021-10-21 11:23:44 -0400
commit77fdc0e56bf9463b432f1a2073ac506a8df9b652 (patch)
tree6954a80b6ce042248893b28327f1e65f2b06fbc9 /clang/lib/CodeGen/CodeGenFunction.cpp
parent5c72323141e4c2935492a9aca728d549c7e544ab (diff)
downloadllvm-77fdc0e56bf9463b432f1a2073ac506a8df9b652.zip
llvm-77fdc0e56bf9463b432f1a2073ac506a8df9b652.tar.gz
llvm-77fdc0e56bf9463b432f1a2073ac506a8df9b652.tar.bz2
[lld-macho] Simplify lc-linker-option.ll and re-enable it on Windows
While attempting to simplify it, I discovered a concerning discrepancy between our handling of LC_LINKER_OPTION vs ld64's. In particular, ld64 does not appear to check for `-all_load` nor `-ObjC` when processing those options. Thus, if/when we fix this behavior, no duplicate symbol error will be expected regardless of the use-after-free. As such, I've removed the test logic that tries to induce the duplicate symbol error. We can just rely on ASAN to do the verification. In order to make the test run on Windows, I've removed the symlink logic. Both ld64 and LLD handle this un-symlinked framework just fine. I also capitalized the framework name, since that's the typical convention. Reviewed By: #lld-macho, oontvoo Differential Revision: https://reviews.llvm.org/D112195
Diffstat (limited to 'clang/lib/CodeGen/CodeGenFunction.cpp')
0 files changed, 0 insertions, 0 deletions