Displaying 8 results from an estimated 8 matches for "noinhibit".
Did you mean:
inhibit
2020 Nov 05
0
[EXTERNAL] [llvm-mc] FreeBSD kernel module performance impact when upgrading clang
> You used -noinhibit-exec to ignore the diagnostic, which is usually a bad thing.
I certainly agree with that.
The point I was trying to make in my original email is that, specifically for kernel objects, this diagnostic is incorrect. R_X86_64_PC32 can be used safely against the symbol foo in that specific context, a...
2020 May 29
2
Range lists, zero-length functions, linker gc
...ection.
> >>
> >
> >Any harm in using -2 everywhere, for consistency?
>
> When resolving a relocation, in certain cases we have to give an undefined
> symbol a value.
> This can happen with:
>
> * an undefined weak symbol
> * an undefined global symbol in --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)
> reloca...
2020 May 29
4
Range lists, zero-length functions, linker gc
...d a -1/-1 pair have a reserved meaning in that section.
>>
>
>Any harm in using -2 everywhere, for consistency?
When resolving a relocation, in certain cases we have to give an undefined symbol a value.
This can happen with:
* an undefined weak symbol
* an undefined global symbol in --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_...
2020 May 29
2
Range lists, zero-length functions, linker gc
...; >Any harm in using -2 everywhere, for consistency?
> >
> > When resolving a relocation, in certain cases we have to give an undefined
> > symbol a value.
> > This can happen with:
> >
> > * an undefined weak symbol
> > * an undefined global symbol in --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 "mos...
2020 May 29
2
Range lists, zero-length functions, linker gc
...> > > When resolving a relocation, in certain cases we have to give an
> > undefined
> > > > symbol a value.
> > > > This can happen with:
> > > >
> > > > * an undefined weak symbol
> > > > * an undefined global symbol in --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 ab...
2020 May 31
2
Range lists, zero-length functions, linker gc
...n cases we have to give an
> >> > undefined
> >> > > > symbol a value.
> >> > > > This can happen with:
> >> > > >
> >> > > > * an undefined weak symbol
> >> > > > * an undefined global symbol in --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 respe...
2020 May 31
3
Range lists, zero-length functions, linker gc
...undefined
> >> >> > > > symbol a value.
> >> >> > > > This can happen with:
> >> >> > > >
> >> >> > > > * an undefined weak symbol
> >> >> > > > * an undefined global symbol in --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
> >> >> > > >
> >...
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