KKeith Smiley[lld-macho] Add support for -w
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[lld] Rename StringRef _lower() method calls to _insensitive() | 4 年前 | |
Re-land [LLD] Remove global state in lldCommon Move all variables at file-scope or function-static-scope into a hosting structure (lld::CommonLinkerContext) that lives at lldMain()-scope. Drivers will inherit from this structure and add their own global state, in the same way as for the existing COFFLinkerContext. See discussion in https://lists.llvm.org/pipermail/llvm-dev/2021-June/151184.html The previous land f860fe362282ed69b9d4503a20e5d20b9a041189 caused issues in https://lab.llvm.org/buildbot/#/builders/123/builds/8383, fixed by 22ee510dac9440a74b2e5b3fe3ff13ccdbf55af3. Differential Revision: https://reviews.llvm.org/D108850 | 4 年前 | |
[lld-macho] Don't include CommandFlags.h in CommonLinkerContext.h Main motivation: including llvm/CodeGen/CommandFlags.h in CommonLinkerContext.h means that the declaration of llvm::Reloc is visible in any file that includes CommonLinkerContext.h. Since our cpp files have both using namespace llvm and using namespace lld::macho, this results in conflicts with lld::macho::Reloc. I suppose we could put llvm::Reloc into a nested namespace, but in general, I think we should avoid transitively including too many header files in a very widely used header like CommonLinkerContext.h. RegisterCodeGenFlags' ctor initializes a bunch of function-static structures and does nothing else, so it should be fine to "initialize" it as a temporary stack variable rather than as a file static. Reviewed By: aganea Differential Revision: https://reviews.llvm.org/D119913 | 4 年前 | |
[LLD] Move duplicated dwarf parsing code to the Common library. NFC. Differential Revision: https://reviews.llvm.org/D69197 llvm-svn: 375390 | 6 年前 | |
[lld-macho] Add support for -w This flag suppresses warnings produced by the linker. In ld64 this has an interesting interaction with -fatal_warnings, it silences the warnings but the link still fails. Instead of doing that here we still print the warning and eagerly fail the link in case both are passed, this seems more reasonable so users can understand why the link fails. Differential Revision: https://reviews.llvm.org/D127564 | 3 年前 | |
[LLD][ELF][Windows] small improvement to D82567 Bail early if there is no existing output file to be overwritten. Differential Revision: https://reviews.llvm.org/D83272 | 5 年前 | |
Re-land [LLD] Remove global state in lldCommon Move all variables at file-scope or function-static-scope into a hosting structure (lld::CommonLinkerContext) that lives at lldMain()-scope. Drivers will inherit from this structure and add their own global state, in the same way as for the existing COFFLinkerContext. See discussion in https://lists.llvm.org/pipermail/llvm-dev/2021-June/151184.html The previous land f860fe362282ed69b9d4503a20e5d20b9a041189 caused issues in https://lab.llvm.org/buildbot/#/builders/123/builds/8383, fixed by 22ee510dac9440a74b2e5b3fe3ff13ccdbf55af3. Differential Revision: https://reviews.llvm.org/D108850 | 4 年前 | |
[lld/mac] Add --reproduce option This adds support for ld.lld's --reproduce / lld-link's /reproduce: flag to the MachO port. This flag can be added to a link command to make the link write a tar file containing all inputs to the link and a response file containing the link command. This can be used to reproduce the link on another machine, which is useful for sharing bug report inputs or performance test loads. Since the linker is usually called through the clang driver and adding linker flags can be a bit cumbersome, setting the env var LLD_REPRODUCE=foo.tar triggers the feature as well. The file response.txt in the archive can be used with ld64.lld.darwinnew $(cat response.txt) as long as the contents are smaller than the command-line limit, or with ld64.lld.darwinnew @response.txt once D92149 is in. The support in this patch is sufficient to create a tar file for Chromium's base_unittests that can link after unpacking on a different machine. Differential Revision: https://reviews.llvm.org/D92274 | 5 年前 | |
[lld] Add support for other demanglers other than Itanium LLVM core library supports demangling other mangled symbols other than itanium, such as D and Rust. LLD should use those demanglers in order to output pretty demangled symbols on error messages. Reviewed By: MaskRay, #lld-macho Differential Revision: https://reviews.llvm.org/D116279 | 4 年前 | |
Cleanup codegen includes This is a (fixed) recommit of https://reviews.llvm.org/D121169 after: 1061034926 before: 1063332844 Discourse thread: https://discourse.llvm.org/t/include-what-you-use-include-cleanup Differential Revision: https://reviews.llvm.org/D121681 | 4 年前 | |
Add missing include to fix modular build | 4 年前 | |
[lld] Remove unused LLD_REPOSITORY Remnant after D72803. Distributions who want to customize the string can customize LLD_VERSION_STRING instead. Reviewed By: #lld-macho, mstorsjo, thakis Differential Revision: https://reviews.llvm.org/D107416 | 4 年前 |