Searched refs:relocations (Results 1 – 25 of 124) sorted by relevance
12345
| /external/llvm/test/MC/Mips/ |
| D | oddspreg.s | 5 # RUN: llvm-readobj -sections -section-data -section-relocations - | \
12 # RUN: llvm-readobj -sections -section-data -section-relocations - | \
21 # RUN: llvm-readobj -sections -section-data -section-relocations - | \
25 # RUN: llvm-readobj -sections -section-data -section-relocations - | \
29 # RUN: llvm-readobj -sections -section-data -section-relocations - | \
33 # RUN: llvm-readobj -sections -section-data -section-relocations - | \
|
| D | higher-highest-addressing.s | 8 # Test that R_MIPS_HIGHER and R_MIPS_HIGHEST relocations are created. By using
10 # relocations.
32 # Check the case where relocations are not modified by adding +1. The constant
|
| D | mips_abi_flags_xx.s | 5 # RUN: llvm-readobj -sections -section-data -section-relocations - | \
9 # RUN: llvm-readobj -sections -section-data -section-relocations - | \
13 # RUN: llvm-readobj -sections -section-data -section-relocations - | \
|
| D | micromips-jump26.s | 8 # for relocations.
16 # Check that the appropriate relocations were created.
|
| D | micromips-tailr.s | 8 # for relocations.
18 # Check that the appropriate relocations were created.
|
| D | micromips-branch-fixup.s | 8 # for relocations.
59 # Check that the appropriate relocations were created.
|
| D | mips-data-directives.s | 5 # RUN: llvm-readobj -sections -section-data -section-relocations - | \
|
| D | micromips-relocations.s | 8 # for relocations.
79 # Check that the appropriate relocations were created.
|
| D | elf_reginfo.s | 12 # Check that the appropriate relocations were created.
|
| /external/llvm/docs/CommandGuide/ |
| D | llvm-readobj.rst | 42 .. option:: -section-relocations, -sr
44 When used with ``-sections``, display relocations for each section shown.
50 .. option:: -relocations, -r
68 When used with ``-relocations``, display each relocation in an expanded
|
| /external/llvm/docs/ |
| D | MCJITDesignAndImplementation.rst | 73 image must be loaded into suitable memory, relocations must be applied and
102 object image and for each section iterates through the relocations for
113 relocations have not yet been applied and the generated code is still not
117 relocations when loadObject completes. However, this shouldn't be
120 relocations are applied. It is possible to apply relocations multiple
148 external symbols and then apply all relocations for the object.
154 iterate through the list of relocations it has stored which are associated
160 sections and for each section iterates through a list of relocations that
163 relocations for which the symbol associated with the relocation is located
168 .. image:: MCJIT-resolve-relocations.png
[all …]
|
| /external/llvm/bindings/python/llvm/ |
| D | object.py | 251 relocations = lib.LLVMGetRelocations(self)
254 if lib.LLVMIsRelocationIteratorAtEnd(self, relocations):
257 last = Relocation(relocations)
263 lib.LLVMMoveToNextRelocation(relocations)
269 lib.LLVMDisposeRelocationIterator(relocations)
|
| /external/llvm/test/MC/PowerPC/ |
| D | ppc64-relocs-01.s | 24 # The relocations in .rela.text are the 'number64' load using a
32 # The .opd entry for the 'access_int64' function creates 2 relocations:
|
| /external/llvm/test/Object/ |
| D | yaml2obj-readobj.test | 1 RUN: yaml2obj %p/Inputs/COFF/i386.yaml | llvm-readobj -file-headers -relocations -expand-relocs - |…
3 RUN: llvm-readobj -file-headers -relocations -expand-relocs %t \
|
| /external/llvm/test/CodeGen/AArch64/ |
| D | extern-weak.ll | 22 ; In the large model, the usual relocations are absolute and can
48 ; In the large model, the usual relocations are absolute and can
|
| D | arm64-extern-weak.ll | 21 ; In the large model, the usual relocations are absolute and can
44 ; In the large model, the usual relocations are absolute and can
|
| D | got-abuse.ll | 7 ; load. Neither of these alternatives has the ELF relocations required to
|
| /external/llvm/test/tools/llvm-objdump/ |
| D | macho-unwind-info-no-relocs.test | 4 # relocations.
|
| /external/llvm/test/DebugInfo/ |
| D | debuglineinfo.test | 6 ; This test verifies that relocations are correctly applied to the
8 ; If relocations are not applied the first two functions will be reported as
|
| /external/valgrind/ |
| D | exp-sgcheck.supp | 2 ld-2.X possibly applying relocations
|
| /external/llvm/test/ExecutionEngine/MCJIT/ |
| D | 2013-04-04-RelocAddend.ll | 3 ; Verify relocations to global symbols with addend work correctly.
|
| /external/llvm/test/MC/MachO/ARM/ |
| D | no-subsections-reloc.s | 6 @ in the same section can be resolved at assembly time w/o relocations.
|
| /external/llvm/test/ExecutionEngine/OrcMCJIT/ |
| D | 2013-04-04-RelocAddend.ll | 3 ; Verify relocations to global symbols with addend work correctly.
|
| /external/llvm/test/MC/ARM/ |
| D | macho-relocs-with-addend.s | 4 @ MachO relocations that end up expressed as internal
|
| /external/llvm/test/DebugInfo/X86/ |
| D | fission-cu.ll | 3 ; RUN: llvm-readobj --relocations %t | FileCheck --check-prefix=OBJ %s
101 ; For x86-64-linux we should have this set of relocations for the debug info section
|
12345