Displaying 9 results from an estimated 9 matches for "r_aarch64_adr_prel_pg_hi21".
2016 Aug 16
3
LLD release note
...;s enough AArch64 to allow lld to self-host and to finish a build
> of the base system on FreeBSD. Last we (I and Rafael) checked, it was
> mid-june timeframe, but nothing changed since then.
FYI when trying to link the FreeBSD/arm64 kernel now I receive tens of
thousands of "relocation R_AARCH64_ADR_PREL_PG_HI21 out of range". Did
you try building the kernel as well, or just userland?
2020 May 29
2
Range lists, zero-length functions, linker gc
...-gc-
> sections implementation can trigger this as well)
> * a relocation referencing an undefined symbol in a non-SHF_ALLOC section
>
> We always respect the addend in a relocation entry for an absolute/PC-
> relative (I can use "most" here)
> relocation (R_ARM_THM_PC8, R_AARCH64_ADR_PREL_PG_HI21, R_X86_64_64,
> local exec TLS relocation types, ...)
> Ignoring the addend (using -2 everywhere) will break this consistency.
>
> The relocated code may do pointer subtraction which would work if addends
> were
> respected, but will break using -2 everywhere.
>I suspect David...
2016 Aug 12
5
LLD release note
I'm compiling a release note for LLD, and I'd like to get you guy's input
about the status of the following subsystems.
- Current MIPS support
- Current AArch64 support
- LTO
I think AArch64 and LTO are added after the last release, so everything
we've made so far should be in the next release note. MIPS's situation is
different though.
Rui
-------------- next part
2020 May 29
4
Range lists, zero-length functions, linker gc
...-noinhibit-exec mode (a buggy --gc-sections implementation can trigger this as well)
* a relocation referencing an undefined symbol in a non-SHF_ALLOC section
We always respect the addend in a relocation entry for an absolute/PC-relative (I can use "most" here)
relocation (R_ARM_THM_PC8, R_AARCH64_ADR_PREL_PG_HI21, R_X86_64_64,
local exec TLS relocation types, ...)
Ignoring the addend (using -2 everywhere) will break this consistency.
The relocated code may do pointer subtraction which would work if addends were
respected, but will break using -2 everywhere.
The relocated code can be allocatable or not. No...
2020 May 29
2
Range lists, zero-length functions, linker gc
...entation can trigger this as well)
> > * a relocation referencing an undefined symbol in a non-SHF_ALLOC section
> >
> > We always respect the addend in a relocation entry for an absolute/PC-
> > relative (I can use "most" here)
> > relocation (R_ARM_THM_PC8, R_AARCH64_ADR_PREL_PG_HI21, R_X86_64_64,
> > local exec TLS relocation types, ...)
> > Ignoring the addend (using -2 everywhere) will break this consistency.
> >
> > The relocated code may do pointer subtraction which would work if addends
> > were
> > respected, but will break using -2 ev...
2020 May 29
2
Range lists, zero-length functions, linker gc
...elocation referencing an undefined symbol in a non-SHF_ALLOC
> > section
> > > >
> > > > We always respect the addend in a relocation entry for an absolute/PC-
> > > > relative (I can use "most" here)
> > > > relocation (R_ARM_THM_PC8, R_AARCH64_ADR_PREL_PG_HI21, R_X86_64_64,
> > > > local exec TLS relocation types, ...)
> > > > Ignoring the addend (using -2 everywhere) will break this consistency.
> > > >
> > > > The relocated code may do pointer subtraction which would work if
> > addends
> > &g...
2020 May 31
2
Range lists, zero-length functions, linker gc
...a non-SHF_ALLOC
> >> > section
> >> > > >
> >> > > > We always respect the addend in a relocation entry for an absolute/PC-
> >> > > > relative (I can use "most" here)
> >> > > > relocation (R_ARM_THM_PC8, R_AARCH64_ADR_PREL_PG_HI21, R_X86_64_64,
> >> > > > local exec TLS relocation types, ...)
> >> > > > Ignoring the addend (using -2 everywhere) will break this consistency.
> >> > > >
> >> > > > The relocated code may do pointer subtraction which would wo...
2020 May 31
3
Range lists, zero-length functions, linker gc
...ection
> >> >> > > >
> >> >> > > > We always respect the addend in a relocation entry for an absolute/PC-
> >> >> > > > relative (I can use "most" here)
> >> >> > > > relocation (R_ARM_THM_PC8, R_AARCH64_ADR_PREL_PG_HI21, R_X86_64_64,
> >> >> > > > local exec TLS relocation types, ...)
> >> >> > > > Ignoring the addend (using -2 everywhere) will break this consistency.
> >> >> > > >
> >> >> > > > The relocated code may d...
2020 May 28
2
Range lists, zero-length functions, linker gc
As has been mentioned elsewhere, Sony generally fixes up references from debug info to stripped functions (of any length) using -1, because that's a less-likely-to-be-real address than 0x0 or 0x1. (0x0 is a typical base address for shared libraries, I'd think using it has the potential to mislead various consumers.) For .debug_ranges we use -2, because both a 0/0 pair and a -1/-1 pair