Home
last modified time | relevance | path

Searched refs:LLD (Results 1 – 25 of 28) sorted by relevance

12

/freebsd/contrib/llvm-project/lld/docs/
H A Dwindows_support.rst17 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 Dindex.rst1 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
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
50 but in LLVM bitcode format. LLD reads bitcode object files, compile
51 them using LLVM and emit an output file. Because in this way LLD can
[all …]
H A DDTLTO.rst10 Currently, DTLTO is only supported in ELF and COFF LLD.
12 ELF LLD
23 backend compilations. The compiler invoked must match the version of LLD.
39 Some LLD LTO options (e.g., ``--lto-sample-profile=<file>``) are supported.
43 COFF LLD
54 backend compilations. The compiler invoked must match the version of LLD.
70 Some LLD LTO options (e.g., ``/lto-sample-profile:<file>``) are supported.
75 as users are expected to invoke LLD directly.
H A Derror_handling_script.rst5 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 DNewLLD.rst7 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 DReleaseNotes.rst35 Mach-O LLD feature of the same name.
H A DPartitions.rst9 LLD's partitioning feature allows a program (which may be an executable
H A DWebAssembly.rst13 The WebAssembly object file format used by LLVM and LLD is specified as part of
/freebsd/contrib/llvm-project/lld/docs/MachO/
H A Dld64-vs-lld.rst2 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 Dindex.rst1 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/contrib/llvm-project/lld/docs/ELF/
H A Dlinker_script.rst4 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 Dwarn_backrefs.rst25 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/share/mk/
H A Dbsd.linker.mk78 _ld_version:=${_ld_version:[*]:C/^.* LLD /LLD /:[@]}
H A Dsrc.opts.mk122 LLD \
/freebsd/tools/build/options/
H A DWITH_LLD_BOOTSTRAP1 Build the LLD linker during the bootstrap phase of the build,
H A DWITHOUT_LLD_BOOTSTRAP1 Do not build the LLD linker during the bootstrap phase of
/freebsd/sys/conf/
H A Dldscript.riscv115 LLD. */
/freebsd/contrib/llvm-project/llvm/lib/Target/Mips/
H A DMipsSERegisterInfo.cpp78 case Mips::LLD: in getLoadStoreOffsetSizeInBits()
H A DMipsExpandPseudo.cpp234 LL = STI->hasMips64r6() ? Mips::LLD_R6 : Mips::LLD; in expandAtomicCmpSwap()
750 LL = STI->hasMips64r6() ? Mips::LLD_R6 : Mips::LLD; in expandAtomicBinOp()
H A DMips32r6InstrFormats.td60 // The spec occasionally names this value LL, LLD, SC, or SCD.
/freebsd/contrib/llvm-project/llvm/include/llvm/DWARFLinker/
H A DDWARFLinker.h
/freebsd/contrib/llvm-project/llvm/lib/CodeGen/SelectionDAG/
H A DDAGCombiner.cpp28418 LoadSDNode *LLD = cast<LoadSDNode>(LHS); in SimplifySelectOps() local
28426 !LLD->isSimple() || !RLD->isSimple() || in SimplifySelectOps()
28429 LLD->isIndexed() || RLD->isIndexed() || in SimplifySelectOps()
28431 LLD->getMemoryVT() != RLD->getMemoryVT() || in SimplifySelectOps()
28433 (LLD->getExtensionType() != RLD->getExtensionType() && in SimplifySelectOps()
28435 LLD->getExtensionType() != ISD::EXTLOAD && in SimplifySelectOps()
28442 LLD->getPointerInfo().getAddrSpace() != 0 || in SimplifySelectOps()
28446 LLD->getBasePtr().getOpcode() == ISD::TargetFrameIndex || in SimplifySelectOps()
28449 LLD->getBasePtr().getValueType())) in SimplifySelectOps()
28453 if (LLD->isPredecessorOf(RLD) || RLD->isPredecessorOf(LLD)) in SimplifySelectOps()
[all …]
/freebsd/contrib/llvm-project/lld/COFF/
H A DOptions.td232 // LLD extensions
/freebsd/contrib/llvm-project/lld/MachO/
H A DOptions.td11 def grp_lld : OptionGroup<"kind">, HelpText<"LLD-SPECIFIC">;
1119 HelpText<"Obsolete. LLD supports LTO directly, without using an external dylib.">,
/freebsd/
H A DUPDATING690 The WITHOUT_LLD_IS_LD option has been removed. When LLD is enabled
1397 Clang/LLVM is now the default compiler and LLD the default
1420 LLD is now the default linker for powerpc64. The change for powerpc64
2333 arm64 builds now use the base system LLD 4.0.0 linker by default,

12