| /freebsd-14.2/contrib/llvm-project/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 39 same as on Unix (.a). LLD can read it. 42 :good:`Done`. LLD creates a DLL if ``/DLL`` option is given. Exported 55 :partial:`Partially done`. LLD currently recognizes these directives: 60 link.exe. However, LLD does not support /DEBUG:FASTLINK. 63 Downloading LLD 70 Building LLD 76 1. Check out LLVM and LLD from the LLVM SVN repository (or Git mirror), [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 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 36 - You can embed LLD in your program to eliminate dependencies on 44 2017, LLD/ELF consists only of 21k lines of C++ code while GNU gold 93 If you haven't checked out LLVM, the easiest way to build LLD is to 105 Using LLD 108 LLD is installed as ``ld.lld``. On Unix, linkers are invoked by 116 ``/usr/bin/ld`` is resolved to LLD. [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 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 115 info, which is roughly 2 GB in output size, LLD reads 122 LLD produces the 2 GB executable in 15 seconds. [all …]
|
| H A D | ReleaseNotes.rst | 30 Without ``--fat-lto-objects``, LLD will link LLVM FatLTO objects using the 90 * LLD now prefers library paths specified with ``-libpath:`` over the implicitly 105 * A new, LLD specific option, ``-lld-allow-duplicate-weak``, was added 137 * LLD no longer tries to autodetect and use library paths from MSVC/WinSDK
|
| H A D | Partitions.rst | 9 LLD's partitioning feature allows a program (which may be an executable
|
| H A D | WebAssembly.rst | 13 The WebAssembly object file format used by LLVM and LLD is specified as part of
|
| /freebsd-14.2/contrib/llvm-project/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 prefer 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.
|
| /freebsd-14.2/contrib/llvm-project/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. 101 only contains symbol assignments (e.g. ``.foo { symbol = 42; }``). LLD will 106 GNU ld sets the ``SHF_WRITE`` flag. LLD sets the SHF_WRITE flag only if the 113 When an *OutputSection* *S* has ``(type)``, LLD will set ``sh_type`` or 194 writable but non-RELRO sections. LLD ignores ``offset`` and ``exp`` and aligns 198 LLD will insert ``.relro_padding`` immediately before the symbol assignment
|
| 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.
|
| /freebsd-14.2/contrib/llvm-project/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
|
| /freebsd-14.2/tools/build/options/ |
| H A D | WITH_LLD_IS_LD | 1 Use LLVM's LLD as the system linker.
|
| H A D | WITH_LLD_BOOTSTRAP | 1 Build the LLD linker during the bootstrap phase of the build,
|
| H A D | WITHOUT_LLD_BOOTSTRAP | 1 Do not build the LLD linker during the bootstrap phase of
|
| /freebsd-14.2/share/mk/ |
| H A D | bsd.linker.mk | 73 _ld_version:=${_ld_version:[*]:C/^.* LLD /LLD /:[@]}
|
| H A D | src.opts.mk | 127 LLD \
|
| /freebsd-14.2/contrib/llvm-project/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()
|
| H A D | Mips32r6InstrFormats.td | 60 // The spec occasionally names this value LL, LLD, SC, or SCD.
|
| /freebsd-14.2/sys/conf/ |
| H A D | ldscript.riscv | 115 LLD. */
|
| /freebsd-14.2/contrib/llvm-project/llvm/lib/CodeGen/SelectionDAG/ |
| H A D | DAGCombiner.cpp | 26901 LoadSDNode *LLD = cast<LoadSDNode>(LHS); in SimplifySelectOps() local 26909 !LLD->isSimple() || !RLD->isSimple() || in SimplifySelectOps() 26912 LLD->isIndexed() || RLD->isIndexed() || in SimplifySelectOps() 26914 LLD->getMemoryVT() != RLD->getMemoryVT() || in SimplifySelectOps() 26918 LLD->getExtensionType() != ISD::EXTLOAD && in SimplifySelectOps() 26925 LLD->getPointerInfo().getAddrSpace() != 0 || in SimplifySelectOps() 26936 if (LLD->isPredecessorOf(RLD) || RLD->isPredecessorOf(LLD)) in SimplifySelectOps() 26950 Worklist.push_back(LLD); in SimplifySelectOps() 26967 if ((LLD->hasAnyUseOfValue(1) && in SimplifySelectOps() 26989 if ((LLD->hasAnyUseOfValue(1) && in SimplifySelectOps() [all …]
|
| /freebsd-14.2/contrib/llvm-project/lld/COFF/ |
| H A D | Options.td | 225 // LLD extensions
|
| /freebsd-14.2/contrib/llvm-project/lld/MachO/ |
| H A D | Options.td | 11 def grp_lld : OptionGroup<"kind">, HelpText<"LLD-SPECIFIC">; 1058 HelpText<"Obsolete. LLD supports LTO directly, without using an external dylib.">,
|
| /freebsd-14.2/ |
| H A D | UPDATING | 126 The WITHOUT_LLD_IS_LD option has been removed. When LLD is enabled 789 Clang/LLVM is now the default compiler and LLD the default 812 LLD is now the default linker for powerpc64. The change for powerpc64 1714 arm64 builds now use the base system LLD 4.0.0 linker by default,
|