Home
last modified time | relevance | path

Searched refs:LTO (Results 1 – 25 of 78) sorted by relevance

1234

/external/clang/docs/
DLTOVisibility.rst2 LTO Visibility
5 *LTO visibility* is a property of an entity that specifies whether it can be
6 referenced from outside the current LTO unit. A *linkage unit* is a set of
8 unit's *LTO unit* is the subset of the linkage unit that is linked together
9 using link-time optimization; in the case where LTO is not being used, the
10 linkage unit's LTO unit is empty. Each linkage unit has only a single LTO unit.
12 The LTO visibility of a class is used by the compiler to determine which
19 ODR violation to define a class with hidden LTO visibility in multiple linkage
20 units. A class with public LTO visibility may be defined in multiple linkage
22 control flow integrity features can only be applied to classes with hidden LTO
[all …]
DControlFlowIntegrity.rst24 As currently implemented, all schemes rely on link-time optimization (LTO);
25 so it is required to specify ``-flto``, and the linker used must support LTO,
34 LTO visibility for that class. LTO visibility is a property of a class that
36 for :doc:`LTO visibility <LTOVisibility>`.
45 <cfi-cross-dso>` exists that does not require classes to have hidden LTO
268 Normally, CFI checks will only be performed for classes that have hidden LTO
/external/llvm/test/tools/dsymutil/
Dbasic-linking.test2 …rbose -oso-prepend-path=%p %p/Inputs/basic-lto.macho.x86_64 | FileCheck %s --check-prefix=CHECK-LTO
4 …hive.macho.x86_64 | FileCheck %s --check-prefix=CHECK --check-prefix=CHECK-LTO --check-prefix=CHEC…
60 ================================= LTO link ================================
61 CHECK-LTO: DEBUG MAP OBJECT: {{.*}}basic-lto.macho.x86_64.o
62 CHECK-LTO: Input compilation unit:
63 CHECK-LTO-NEXT: TAG_compile_unit
64 CHECK-LTO-NOT: TAG
65 CHECK-LTO: AT_name {{.*}}basic1.c
66 CHECK-LTO: Input compilation unit:
67 CHECK-LTO-NEXT: TAG_compile_unit
[all …]
Ddebug-map-parsing.test2 …g-map -oso-prepend-path=%p %p/Inputs/basic-lto.macho.x86_64 | FileCheck %s --check-prefix=CHECK-LTO
30 CHECK-LTO-NOT: error
31 CHECK-LTO: ---
32 CHECK-LTO: triple: 'x86_64-apple-darwin'
33 CHECK-LTO: binary-path:{{.*}}/Inputs/basic-lto.macho.x86_64
34 CHECK-LTO: /Inputs/basic-lto.macho.x86_64.o
35 CHECK-LTO-DAG: sym: _bar, objAddr: 0x0000000000000050, binAddr: 0x0000000100000F90, size: 0x000000…
36 CHECK-LTO-DAG: sym: _baz, objAddr: 0x0000000000000658, binAddr: 0x0000000100001000, size: 0x000000…
37 CHECK-LTO-DAG: sym: _foo, objAddr: 0x0000000000000010, binAddr: 0x0000000100000F50, size: 0x000000…
38 CHECK-LTO-DAG: sym: _main, objAddr: 0x0000000000000000, binAddr: 0x0000000100000F40, size: 0x00000…
[all …]
/external/llvm/test/tools/llvm-nm/X86/
DIRobj.test3 # CHECK: ---------------- (LTO,RODATA) external _global_const
4 # CHECK: ---------------- (LTO,DATA) external _global_data
5 # CHECK: ---------------- (LTO,CODE) external _global_func
6 # CHECK: ---------------- (LTO,RODATA) private external _hidden_const
7 # CHECK: ---------------- (LTO,DATA) private external _hidden_data
8 # CHECK: ---------------- (LTO,CODE) private external _hidden_func
9 # CHECK: ---------------- (LTO,RODATA) non-external _static_const
10 # CHECK: ---------------- (LTO,DATA) non-external _static_data
11 # CHECK: ---------------- (LTO,CODE) non-external _static_func
/external/llvm/tools/lto/
DCMakeLists.txt5 LTO
19 add_llvm_library(LTO SHARED ${SOURCES})
23 COMPONENT LTO)
30 set_property(TARGET LTO APPEND_STRING PROPERTY
/external/compiler-rt/test/safestack/
DCMakeLists.txt8 # Some tests require LTO, so add a dependency on the relevant LTO plugin.
16 LTO
/external/llvm/lib/LTO/
DLLVMBuild.txt1 ;===- ./lib/LTO/LLVMBuild.txt ----------------------------------*- Conf -*--===;
20 name = LTO
DCMakeLists.txt51 LTO.cpp
59 ${LLVM_MAIN_INCLUDE_DIR}/llvm/LTO
/external/llvm/docs/
DGoldPlugin.rst9 the system linker. LTO support on Linux systems requires that you use the
10 `gold linker`_ which supports LTO via plugins. This is the same mechanism
11 used by the `GCC LTO`_ project.
18 .. _`GCC LTO`: http://gcc.gnu.org/wiki/LinkTimeOptimization
125 Quickstart for using LTO with autotooled projects
129 everything is in place for an easy to use LTO build of autotooled projects:
DLinkTimeOptimization.rst12 time. Link Time Optimization (LTO) is another name for intermodular
14 interface and design between the LTO optimizer and the linker.
35 The following example illustrates the advantages of LTO's integrated approach
36 and clean interface. This example requires a system linker which supports LTO
163 the LLVM LTO code to be updated independently of the linker tool. On platforms
178 After symbol resolution, the linker tells the LTO shared object which symbols
/external/llvm/test/LTO/X86/
Dcfi_endproc.ll19 ; Without -exported-symbol, main should be eliminated by LTO.
20 ; With -exported-symbol=main, main should be preserved by LTO.
Dtriple-init.ll12 ; We check that LTO will be aware of target triple and apply pow to __exp10 transformation.
Ddiagnostic-handler-noexit.ll1 ; LTO default diagnostic handler should be non-exiting.
/external/llvm/tools/llvm-lto/
DCMakeLists.txt7 LTO
DLLVMBuild.txt22 required_libraries = BitWriter Core IRReader LTO Object Support all-targets
/external/clang/include/clang/Driver/
DTypes.def77 // LLVM IR/LTO types. We define separate types for IR and LTO because LTO
/external/swiftshader/third_party/LLVM/tools/gold/
DMakefile29 CXXFLAGS+=$(SharedLibDir)/$(SharedPrefix)LTO$(SHLIBEXT)
/external/llvm/test/
DCMakeLists.txt86 if(TARGET LTO)
87 set(LLVM_TEST_DEPENDS ${LLVM_TEST_DEPENDS} LTO)
/external/llvm/test/tools/gold/X86/
Dinvalid.ll6 ; CHECK: error: LLVM gold plugin has failed to create LTO module: Malformed block
/external/llvm/tools/gold/
DCMakeLists.txt13 LTO
DREADME.txt1 The LLVM Gold LTO Plugin
/external/llvm/lib/
DCMakeLists.txt10 add_subdirectory(LTO)
DLLVMBuild.txt31 LTO
/external/swiftshader/third_party/LLVM/tools/lto/
DMakefile11 LIBRARYNAME = LTO

1234