search for: r_type

...ruct { Elf64_Addr r_offset; Elf64_Xword r_info; Elf64_Sxword r_addend; } Elf64_Rela; Whereas N64 has the following format: typedef struct { Elf64_Addr r_offset; /* Address of reference */ Elf64_Word r_sym; /* Symbol index */ Elf64_Byte r_ssym; /* Special symbol */ Elf64_Byte r_type3; /* Relocation type */ Elf64_Byte r_type2; /* Relocation type */ Elf64_Byte r_type; /* Relocation type */ } Elf64_Rel; typedef struct { Elf64_Addr r_offset; /* Address of reference */ Elf64_Word r_sym; /* Symbol index */ Elf64_Byte r_ssym; /* Special symbol */ Elf64_Byte r_...

...)); +} static int do_reloc64(struct section *sec, Elf_Rel *rel, ElfW(Sym) *sym, const char *symname) @@ -895,8 +905,12 @@ static int do_reloc64(struct section *sec, Elf_Rel *rel, ElfW(Sym) *sym, * the relocations are processed. * Make sure that the offset will fit. */ - if (r_type != R_X86_64_64 && (int32_t)offset != (int64_t)offset) + if (r_type != R_X86_64_64 && + (int32_t)offset != (int64_t)offset) { + if (is_in_xenpvh_assembly(offset)) + break; die("Relocation offset doesn't fit in 32 bits\n"); + } if (r_type == R_X86_64...

...ation of a very specific kind of relocations used by MIPS N64 ABI. As usual the main problem is how to pass target specific data over Native/YAML conversion barrier. In this ABI relocation record r_info field in fact consists of five subfields: * r_sym - symbol index * r_ssym - special symbol * r_type3 - third relocation type * r_type2 - second relocation type * r_type - first relocation type Up to three these relocations applied one by one. The first relocation uses an addendum from the relocation record. Each subsequent relocation takes as its addend the result of the previous operation. Onl...

...sual the main problem is how to pass target >> specific >> data over Native/YAML conversion barrier. >> >> In this ABI relocation record r_info field in fact consists of five >> subfields: >> * r_sym - symbol index >> * r_ssym - special symbol >> * r_type3 - third relocation type >> * r_type2 - second relocation type >> * r_type - first relocation type >> >> Up to three these relocations applied one by one. The first relocation >> uses >> an addendum from the relocation record. Each subsequent relocation takes &g...

...> used by MIPS N64 ABI. As usual the main problem is how to pass target > specific > data over Native/YAML conversion barrier. > > In this ABI relocation record r_info field in fact consists of five > subfields: > * r_sym - symbol index > * r_ssym - special symbol > * r_type3 - third relocation type > * r_type2 - second relocation type > * r_type - first relocation type > > Up to three these relocations applied one by one. The first relocation > uses > an addendum from the relocation record. Each subsequent relocation takes > as > its addend th...

...gt; >>> data over Native/YAML conversion barrier. > >>> > >>> In this ABI relocation record r_info field in fact consists of five > >>> subfields: > >>> * r_sym - symbol index > >>> * r_ssym - special symbol > >>> * r_type3 - third relocation type > >>> * r_type2 - second relocation type > >>> * r_type - first relocation type > >>> > >>> Up to three these relocations applied one by one. The first relocation > >>> uses > >>> an addendum from the...

...he main problem is how to pass target specific >>> data over Native/YAML conversion barrier. >>> >>> In this ABI relocation record r_info field in fact consists of five subfields: >>> * r_sym - symbol index >>> * r_ssym - special symbol >>> * r_type3 - third relocation type >>> * r_type2 - second relocation type >>> * r_type - first relocation type >>> >>> Up to three these relocations applied one by one. The first relocation uses >>> an addendum from the relocation record. Each subsequent relocati...

...ier. > >> >>> > >> >>> In this ABI relocation record r_info field in fact consists of five > >> >>> subfields: > >> >>> * r_sym - symbol index > >> >>> * r_ssym - special symbol > >> >>> * r_type3 - third relocation type > >> >>> * r_type2 - second relocation type > >> >>> * r_type - first relocation type > >> >>> > >> >>> Up to three these relocations applied one by one. The first > relocation > >> >&gt...

...gt;>> >> >> >>> In this ABI relocation record r_info field in fact consists of five >> >> >>> subfields: >> >> >>> * r_sym - symbol index >> >> >>> * r_ssym - special symbol >> >> >>> * r_type3 - third relocation type >> >> >>> * r_type2 - second relocation type >> >> >>> * r_type - first relocation type >> >> >>> >> >> >>> Up to three these relocations applied one by one. The first >> relocation &...

...t;>> data over Native/YAML conversion barrier. >>>>> >>>>> In this ABI relocation record r_info field in fact consists of five >> subfields: >>>>> * r_sym - symbol index >>>>> * r_ssym - special symbol >>>>> * r_type3 - third relocation type >>>>> * r_type2 - second relocation type >>>>> * r_type - first relocation type >>>>> >>>>> Up to three these relocations applied one by one. The first relocation >> uses >>>>> an addendum fro...

Changes: - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce

Changes: - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce

These patches make the changes necessary to build the kernel as Position Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below the top 2G of the virtual address space. It allows to optionally extend the KASLR randomization range from 1G to 3G. Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler changes, PIE support and KASLR in general. Thanks to

These patches make the changes necessary to build the kernel as Position Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below the top 2G of the virtual address space. It allows to optionally extend the KASLR randomization range from 1G to 3G. Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler changes, PIE support and KASLR in general. Thanks to

Changes: - patch v3: - Update on message to describe longer term PIE goal. - Minor change on ftrace if condition. - Changed code using xchgq. - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace

Changes: - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce dynamic relocation space on mapped memory. It also simplifies the relocation process. - Move the start the module section next to the kernel. Remove the need for -mcmodel=large on modules. Extends

Changes: - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce dynamic relocation space on mapped memory. It also simplifies the relocation process. - Move the start the module section next to the kernel. Remove the need for -mcmodel=large on modules. Extends

...b2ac6b3..cb12902 100644 --- a/include/llvm/Support/MachO.h +++ b/include/llvm/Support/MachO.h @@ -402,6 +402,21 @@ namespace llvm { ARM_THUMB_32BIT_BRANCH = 7, // obsolete ARM_RELOC_HALF = 8, ARM_RELOC_HALF_SECTDIFF = 9, + + // Constant values for r_type field in an arm64 architecture + ARM64_RELOC_UNSIGNED = GENERIC_RELOC_VANILLA, // for pointers + ARM64_RELOC_SUBTRACTOR = 1, // must be followed by a ARM64_RELOC_UNSIGNED + ARM64_RELOC_BRANCH26 =2, // a B/BL instruction with 26-bit displacement + ARM64_RELOC_PAGE...

...s ABI relocation record r_info field in fact consists of >>>> five >>>> >> >>> subfields: >>>> >> >>> * r_sym - symbol index >>>> >> >>> * r_ssym - special symbol >>>> >> >>> * r_type3 - third relocation type >>>> >> >>> * r_type2 - second relocation type >>>> >> >>> * r_type - first relocation type >>>> >> >>> >>>> >> >>> Up to three these relocations applied one by one....