/external/clang/docs/ |
D | LTOVisibility.rst | 2 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 …]
|
D | ControlFlowIntegrity.rst | 24 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/ |
D | basic-linking.test | 2 …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 …]
|
D | debug-map-parsing.test | 2 …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/ |
D | IRobj.test | 3 # 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/ |
D | CMakeLists.txt | 5 LTO 19 add_llvm_library(LTO SHARED ${SOURCES}) 23 COMPONENT LTO) 30 set_property(TARGET LTO APPEND_STRING PROPERTY
|
/external/compiler-rt/test/safestack/ |
D | CMakeLists.txt | 8 # Some tests require LTO, so add a dependency on the relevant LTO plugin. 16 LTO
|
/external/swiftshader/third_party/llvm-10.0/llvm/include/llvm/LTO/ |
D | LTO.h | 98 class LTO; variable 110 friend LTO; 133 friend LTO; variable 268 class LTO { 277 LTO(Config Conf, ThinBackend Backend = nullptr, 279 ~LTO();
|
/external/swiftshader/third_party/llvm-10.0/llvm/lib/LTO/ |
D | CMakeLists.txt | 3 LTO.cpp 12 ${LLVM_MAIN_INCLUDE_DIR}/llvm/LTO
|
D | LTO.cpp | 469 LTO::RegularLTOState::RegularLTOState(unsigned ParallelCodeGenParallelismLevel, in RegularLTOState() 475 LTO::ThinLTOState::ThinLTOState(ThinBackend Backend) in ThinLTOState() 482 LTO::LTO(Config Conf, ThinBackend Backend, in LTO() function in LTO 489 LTO::~LTO() = default; 493 void LTO::addModuleToGlobalRes(ArrayRef<InputFile::Symbol> Syms, in addModuleToGlobalRes() 570 Error LTO::add(std::unique_ptr<InputFile> Input, in add() 589 Error LTO::addModule(InputFile &Input, unsigned ModI, in addModule() 663 Expected<LTO::RegularLTOState::AddedModule> 664 LTO::addRegularLTO(BitcodeModule BM, ArrayRef<InputFile::Symbol> Syms, in addRegularLTO() 780 Error LTO::linkRegularLTO(RegularLTOState::AddedModule Mod, in linkRegularLTO() [all …]
|
D | LLVMBuild.txt | 1 ;===- ./lib/LTO/LLVMBuild.txt ----------------------------------*- Conf -*--===; 19 name = LTO
|
/external/pigweed/docs/ |
D | size_optimizations.rst | 586 optimization settings, however this at least gives it the option. Note that LTO 593 Link Time Optimization (LTO) 595 **Summary: LTO can decrase your binary size, at a cost: LTO makes debugging 597 informative. We advise only enabling LTO when absolutely necessary.** 599 Link time optimization (LTO) moves some optimizations from the individual 603 LTO can both increase performance and reduce binary size for embedded projects. 604 This appears to be a strict improvement; and one might think enabling LTO at 605 all times is the best approach. However, this is not the case; in practice, LTO 608 **LTO benefits** 619 **LTO costs** [all …]
|
/external/llvm/lib/LTO/ |
D | LLVMBuild.txt | 1 ;===- ./lib/LTO/LLVMBuild.txt ----------------------------------*- Conf -*--===; 20 name = LTO
|
D | CMakeLists.txt | 51 LTO.cpp 59 ${LLVM_MAIN_INCLUDE_DIR}/llvm/LTO
|
/external/llvm/docs/ |
D | GoldPlugin.rst | 9 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:
|
D | LinkTimeOptimization.rst | 12 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/ |
D | cfi_endproc.ll | 19 ; Without -exported-symbol, main should be eliminated by LTO. 20 ; With -exported-symbol=main, main should be preserved by LTO.
|
/external/AFLplusplus/docs/ |
D | features.md | 52 bytes the larger the target is. Our default instrumentation in LTO and 62 J. An LTO feature that creates a fuzzing dictionary based on comparisons found 80 4. With pcguard mode and LTO mode for LLVM 11 and newer 82 6. Not compatible with LTO instrumentation and needs at least LLVM v4.1 83 7. Automatic in LTO mode with LLVM 11 and newer, an extra pass for all LLVM
|
/external/AFLplusplus/src/ |
D | afl-cc.c | 108 LTO = 1, enumerator 330 compiler_mode = LTO; in edit_params() 432 if (compiler_mode == LLVM || compiler_mode == LTO) { in edit_params() 1260 compiler_mode = LTO; in main() 1302 compiler_mode = LTO; in main() 1364 compiler_mode = LTO; in main() 1709 compiler_mode = LTO; in main() 1782 compiler_mode == LTO ? " [SELECTED]" : "", in main() 1998 if (compiler_mode == LTO) { in main()
|
/external/clang/include/clang/Driver/ |
D | Types.def | 77 // LLVM IR/LTO types. We define separate types for IR and LTO because LTO
|
/external/python/cpython2/Misc/NEWS.d/next/Build/ |
D | 2018-06-15-18-18-16.bpo-30345.j-xRE1.rst | 1 Add -g to LDFLAGS when compiling with LTO to get debug symbols.
|
/external/AFLplusplus/instrumentation/ |
D | README.lto.md | 37 * To instrument at link time, we compile in LTO (link time optimization) mode. 39 LTO options and runs our own afl-ld linker instead of the system linker. 40 * The LLVM linker collects all LTO files to link and instruments them so that we 56 afl-clang-lto++2.63d by Marc "vanHauser" Heuse <mh@mh-sec.de> in mode LTO 288 clang LTO files. The solution is simple: when you `./configure`, you also have 321 * Anything that does not compile with LTO, afl-clang-lto cannot compile either - 325 llvm12 and LTO enabled (`CC=clang-12`, `CXX=clang++-12`, `CFLAGS=-flto=full`, 345 LTO time instrumentation worked, however, "how" the basic blocks were
|
/external/llvm/tools/llvm-lto/ |
D | CMakeLists.txt | 7 LTO
|
/external/llvm/test/ |
D | CMakeLists.txt | 86 if(TARGET LTO) 87 set(LLVM_TEST_DEPENDS ${LLVM_TEST_DEPENDS} LTO)
|
/external/llvm/test/tools/gold/X86/ |
D | invalid.ll | 6 ; CHECK: error: LLVM gold plugin has failed to create LTO module: Malformed block
|