Lines Matching refs:section

17     Elf64_Addr    r_offset;  // Offset from the beginning of section.
23   int g1 __attribute__((section("sec")));
24   int g2 __attribute__((section("sec")));
25   static volatile int l1 __attribute__((section("sec")));
26   static volatile int l2 __attribute__((section("sec")));
55   Relocation section '.rel.text' at offset 0x190 contains 4 entries:
83 from the start of ``.data`` section.
86 and ``l2``. From ``.rel.text`` section above, it is not clear
89 and represents a section. So for static variable or function,
90 the section offset is written to the original insn
92 above insn ``7`` and ``11``, they have section offset ``8`` and ``12``.
97 and is the section offset or some computation result based on
98 section offset for static variables/functions. The non-section-offset
116 The actual to-be-relocated data (0 or section offset)
120 means the section offset must be less than or equal to ``UINT32_MAX`` and this
135 Type ``R_BPF_64_32`` is used for call instruction. The call target section
145   __attribute__((noinline)) __attribute__((section("sec1")))
149   static __attribute__((noinline)) __attribute__((section("sec1")))
153   int global __attribute__((section("sec2")));
161   Disassembly of section .text:
180   Disassembly of section sec1:
194 The second relocation corresponds to ``lfunc(a, b)`` where ``lfunc`` has a section
196 The third relocation corresponds to ld_imm64 of ``global``, which has a section
205 relocation below in ``.data`` section with command
208   Relocation section '.rel.data' at offset 0x458 contains 1 entries:
212 The relocation says the first 8-byte of ``.data`` section should be
218   Relocation section '.rel.debug_info' at offset 0x468 contains 13 entries:
233   Relocation section '.rel.BTF' at offset 0x538 contains 1 entries:
237   Relocation section '.rel.BTF.ext' at offset 0x548 contains 2 entries: