| /openbsd-src/gnu/llvm/lld/docs/ |
| H A D | windows_support.rst | 17 LLD supports Windows operating system. When invoked as ``lld-link.exe`` or with 19 command line options, and it drives further linking processes. LLD accepts 23 The current status is that LLD is used to link production builds of large 34 :good:`Done`. LLD can read import libraries needed to link against DLL. Both 39 same as on Unix (.a). LLD can read it. 42 :good:`Done`. LLD creates a DLL if ``/DLL`` option is given. Exported 48 :good:`Done`. If an ``.res`` file is given, LLD converts the file to a COFF 55 :partial:`Partially done`. LLD currently recognizes these directives: 59 :good:`Done`. LLD can emit PDBs that are at parity with those generated by 60 link.exe. However, LLD does not support /DEBUG:FASTLINK. [all …]
|
| H A D | index.rst | 1 LLD - The LLVM Linker 4 LLD is a linker from the LLVM project that is a drop-in replacement 9 WebAssembly in descending order of completeness. Internally, LLD consists of 18 - LLD is a drop-in replacement for the GNU linkers that accepts the 21 - LLD is very fast. When you link a large program on a multicore 22 machine, you can expect that LLD runs more than twice as fast as the GNU 35 - You can embed LLD in your program to eliminate dependencies on 43 2017, LLD/ELF consists only of 21k lines of C++ code while GNU gold 49 but in LLVM bitcode format. LLD reads bitcode object files, compile 50 them using LLVM and emit an output file. Because in this way LLD can [all …]
|
| H A D | error_handling_script.rst | 5 LLD provides the ability to hook into some error handling routines through a 20 LLD calls the error handling script using the following arguments:: 26 - ``missing-lib``: indicates that LLD failed to find a library. The library name 38 interpreted as an error and reported to the user. In both cases, LLD still
|
| H A D | NewLLD.rst | 7 You can embed LLD to your program by linking against it and calling the linker's 28 This is a list of design choices we've made for ELF and COFF LLD. 61 LLD's handling of archive files (the files with ".a" file extension) is 64 problem is, and how LLD approached the problem. 95 Here is how LLD approaches the problem. Instead of memorizing only undefined 96 symbols, we program LLD so that it memorizes all symbols. When it sees an 99 it. It is doable because LLD does not forget symbols it has seen in archive 102 We believe that LLD's way is efficient and easy to justify. 104 The semantics of LLD's archive handling are different from the traditional 113 I'll give you the list of objects and their numbers LLD has to read and process [all …]
|
| H A D | ReleaseNotes.rst | 74 * Improvements to the PCH.OBJ files handling. Now LLD behaves the same as MSVC
|
| H A D | Partitions.rst | 9 LLD's partitioning feature allows a program (which may be an executable
|
| /openbsd-src/gnu/llvm/lld/docs/MachO/ |
| H A D | ld64-vs-lld.rst | 2 ld64 vs LLD-MachO 6 and LLD-MachO. 10 ld64 strips dead code before reporting duplicate symbols. By default, LLD does 12 to follow it. But, to make adoption easy, LLD can mimic this behavior via 20 - LLD: This turns off ICF and string merging in the linker. 24 LLD is `slightly less conservative about aligning cstrings 30 There are differences in how LLD and ld64 handle ObjC symbols loaded from 38 - LLD: Duplicate symbols, regardless of which archives they are from, will 45 result in duplicate symbol errors. LLD does not check for duplicate aliases; 54 environment variable. LLD flips this default to perfer hermetic builds, but
|
| H A D | index.rst | 1 Mach-O LLD Port 4 LLD is a linker from the LLVM project that is a drop-in replacement 12 - LLD is a drop-in replacement for Apple's Mach-O linker, ld64, that accepts the 15 - LLD is very fast. When you link a large program on a multicore 16 machine, you can expect that LLD runs more than twice as fast as the ld64 22 LLD is available as a pre-built binary by going to the `latest release <https://github.com/llvm/llv… 31 The easiest way to build LLD is to 47 Using LLD 50 LLD can be used by adding ``-fuse-ld=/path/to/ld64.lld`` to the linker flags.
|
| /openbsd-src/gnu/llvm/lld/cmake/modules/ |
| H A D | AddLLD.cmake | 17 get_target_export_arg(${name} LLD export_to_lldtargets) 47 get_target_export_arg(${name} LLD export_to_lldtargets) 63 llvm_add_tool_symlink(LLD ${name} ${dest} ALWAYS_GENERATE) 65 llvm_install_symlink(LLD ${name} ${dest} ALWAYS_GENERATE)
|
| H A D | CMakeLists.txt | 9 "Path for CMake subdirectory for LLD (defaults to '${CMAKE_INSTALL_PACKAGEDIR}/lld')") 46 get_config_exports_includes(LLD LLD_CONFIG_INCLUDE_EXPORTS) 60 install_distribution_exports(LLD)
|
| H A D | LLDConfig.cmake.in | 1 # This file allows users to call find_package(LLD) and pick up our targets.
|
| /openbsd-src/gnu/llvm/lld/docs/ELF/ |
| H A D | linker_script.rst | 4 LLD implements a large subset of the GNU ld linker script notation. The LLD 17 it is appropriate for LLD. Intentional deviations will be documented in this 61 command is followed by ``INSERT``, LLD applies built-in rules which are similar 90 When an *OutputSection* *S* has ``address``, LLD will set sh_addr to ``address``. 96 The presence of ``address`` can cause the condition unsatisfied. LLD will warn. 103 When an *OutputSection* *S* has ``(type)``, LLD will set ``sh_type`` or
|
| H A D | warn_backrefs.rst | 25 LLD remembers the symbol table of archives that it has previously seen, so if 26 there is a reference from an input file to the right of an archive, LLD will 33 LLD that will fail with GNU ld, or even worse both links succeed but they have 38 where LLD and GNU ld archive selection may differ.
|
| /openbsd-src/gnu/llvm/lld/ |
| H A D | CODE_OWNERS.TXT | 2 particular part of LLD are reviewed, either by themself or by someone else. 3 They are also the gatekeepers for their part of LLD, with the final word on
|
| H A D | CMakeLists.txt | 9 # If we are not building as a part of LLVM, build LLD as an 132 # Compute the LLD version from the LLVM version. 135 message(STATUS "LLD version: ${LLD_VERSION}")
|
| /openbsd-src/gnu/llvm/clang/cmake/caches/ |
| H A D | 3-stage-base.cmake | 8 # Use LLD to have fewer requirements on system linker, unless we're on an apple 13 # s390/SystemZ is unsupported by LLD, so don't try to enable LTO if it
|
| /openbsd-src/gnu/llvm/lld/Common/ |
| H A D | CMakeLists.txt | 13 COMMAND ${CMAKE_COMMAND} "-DNAMES=LLD"
|
| /openbsd-src/gnu/llvm/llvm/utils/lit/tests/Inputs/lld-features/ |
| H A D | lit.cfg | 12 # The current directory contains files for each version of LLD, both with and
|
| /openbsd-src/gnu/llvm/llvm/utils/gn/secondary/lld/Common/ |
| H A D | BUILD.gn | 12 names = [ "LLD" ]
|
| /openbsd-src/gnu/llvm/llvm/utils/gn/build/toolchain/ |
| H A D | compiler.gni | 23 # Set this to true to link with LLD instead of the default linker.
|
| /openbsd-src/gnu/llvm/llvm/docs/ |
| H A D | HowToBuildWindowsItaniumPrograms.rst | 23 * LLD 32 * COFF LLD with support for the -autoimport switch. 58 programs to link we currently rely on the -auto-import switch in LLD to auto-import
|
| H A D | HowToAddABuilder.rst | 218 Use Ninja & LLD 220 parallel builds. LLD helps to reduce both link times and memory usage
|
| /openbsd-src/gnu/llvm/llvm/lib/Target/Mips/ |
| H A D | MipsSERegisterInfo.cpp | 82 case Mips::LLD: in getLoadStoreOffsetSizeInBits()
|
| H A D | MipsExpandPseudo.cpp | 235 LL = STI->hasMips64r6() ? Mips::LLD_R6 : Mips::LLD; in expandAtomicCmpSwap() 619 LL = STI->hasMips64r6() ? Mips::LLD_R6 : Mips::LLD; in expandAtomicBinOp()
|
| /openbsd-src/gnu/llvm/llvm/tools/llvm-dwarfutil/ |
| H A D | DebugInfoLinker.cpp | 346 DWARFLinker DebugInfoLinker(&OutStreamer, DwarfLinkerClient::LLD); in linkDebugInfo()
|