Home
last modified time | relevance | path

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

12345

/llvm-project-15.0.7/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
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 Dindex.rst1 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
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
92 If you haven't checked out LLVM, the easiest way to build LLD is to
104 Using LLD
107 LLD is installed as ``ld.lld``. On Unix, linkers are invoked by
115 ``/usr/bin/ld`` is resolved to LLD.
[all …]
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
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 …]
/llvm-project-15.0.7/lld/MachO/
H A Dld64-vs-lld.rst2 LD64 vs LLD-MACHO
5 This doc lists all significant deliberate differences in behavior between LD64 and LLD-MachO.
9 LD64 always deduplicates string literals. LLD only does it when the ``--icf=``
18 LLD is slightly less conservative about aligning cstrings, allowing it to pack
26 - LLD
31 There are differences in how LLD and LD64 handle ObjC symbols loaded from archives.
36 - LLD:
/llvm-project-15.0.7/lld/cmake/modules/
H A DAddLLD.cmake17 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 DCMakeLists.txt9 "Path for CMake subdirectory for LLD (defaults to '${CMAKE_INSTALL_PACKAGEDIR}/lld')")
41 get_config_exports_includes(LLD LLD_CONFIG_INCLUDE_EXPORTS)
51 install_distribution_exports(LLD)
H A DLLDConfig.cmake.in1 # This file allows users to call find_package(LLD) and pick up our targets.
/llvm-project-15.0.7/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.
103 When an *OutputSection* *S* has ``(type)``, LLD will set ``sh_type`` or
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.
/llvm-project-15.0.7/compiler-rt/test/fuzzer/
H A Dgc-sections.test2 # LLD isn't pruning functions as we expect it to with ASAN on i386.
9 With gc-sections. Currently, we can't remove unused code except with LLD.
/llvm-project-15.0.7/clang/test/Driver/
H A Dhip-toolchain-rdc-separate.hip90 // RUN: 2>&1 | FileCheck -check-prefixes=LINK,LINK-HOST-UNBUNDLE,LLD-TMP,LINK-BUNDLE,LINK-EMBED %s
96 // RUN: 2>&1 | FileCheck -check-prefixes=LINK,LLD-TMP,LINK-BUNDLE,LINK-NOEMBED %s
102 // RUN: 2>&1 | FileCheck -check-prefixes=LINK,LLD-FIN,LINK-NOBUNDLE,LINK-NOEMBED %s
129 // LLD-TMP-SAME: "-o" "[[IMG_DEV1:.*.out]]"
130 // LLD-FIN-SAME: "-o" "[[IMG_DEV1:a.out-.*gfx803]]"
138 // LLD-TMP-SAME: "-o" "[[IMG_DEV2:.*.out]]"
139 // LLD-FIN-SAME: "-o" "[[IMG_DEV1:a.out-.*gfx900]]"
H A Dhip-toolchain-mllvm.hip21 // RDC: [[LLD:".*lld.*"]] {{.*}} "-plugin-opt=-amdgpu-function-calls=0"
30 // RDC: [[LLD:".*lld.*"]] {{.*}} "-plugin-opt=-amdgpu-function-calls=0"
H A Dhip-toolchain-device-only.hip15 // CHECK: [[LLD: ".*lld.*"]] "-flavor" "gnu" "--no-undefined" "-shared"
24 // CHECK: [[LLD]] "-flavor" "gnu" "--no-undefined" "-shared"
H A Dhip-toolchain-no-rdc.hip62 // CHECK: [[LLD: ".*lld.*"]] "-flavor" "gnu" "--no-undefined" "-shared"
85 // CHECK: [[LLD]] "-flavor" "gnu" "--no-undefined" "-shared"
125 // CHECK: [[LLD]] "-flavor" "gnu" "--no-undefined" "-shared"
148 // CHECK: [[LLD]] "-flavor" "gnu" "--no-undefined" "-shared"
H A Dhip-target-id.hip37 // CHECK: [[LLD:"[^"]*lld[^"]*"]] {{.*}} "-plugin-opt=mcpu=gfx908"
45 // CHECK: [[LLD]] {{.*}} "-plugin-opt=mcpu=gfx908"
/llvm-project-15.0.7/lld/
H A DCODE_OWNERS.TXT2 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
/llvm-project-15.0.7/clang/cmake/caches/
H A D3-stage-base.cmake8 # 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
/llvm-project-15.0.7/lld/test/ELF/lto/
H A Dthinlto-emit-index.ll36 ;; Test that LLD generates an empty index even for lazy object file that is not added to link.
37 ;; Test that LLD also generates empty imports file with the --thinlto-emit-imports-files option.
45 ;; Ensure LLD generates an empty index for each bitcode file even if all bitcode files are lazy.
52 ;; Test that LLD errors out when run with suffix replacement, or prefix replacement
H A Dthinlto-index-only.ll31 ;; Test that LLD generates an empty index even for lazy object file that is not added to link.
32 ;; Test LLD generates empty imports file either because of thinlto-emit-imports-files option.
39 ;; Ensure LLD generates an empty index for each bitcode file even if all bitcode files are lazy.
/llvm-project-15.0.7/lld/test/MachO/
H A Ddiscard-llvm-sections.s6 ## "_llvm." symbols are not special. LLD would produce duplicate symbol errors
9 ## 1/ Test that LLD does not produce duplicate symbols errors when linking global symbols
H A Ddriver.test2 VERSION: LLD
H A Ddwarf-no-compile-unit.s3 ## Check that LLD does not crash if it encounters DWARF sections
/llvm-project-15.0.7/lld/test/COFF/
H A Ddriver-windows.test2 # RUN: env LLD_IN_TEST=1 not LLD-LINK 2>&1 | FileCheck %s
/llvm-project-15.0.7/lld/test/ELF/
H A Dcrash-report.test3 ## Test the diagnostics produced when LLD crashes.

12345