Displaying 4 results from an estimated 4 matches for "global_offset_tableatom".
2013 Oct 21
1
[LLVMdev] [lld] Handle _GLOBAL_OFFSET_TABLE symbol
The Hexagon target adds new atom using the addAbsoluteAtom() functions
and then assigns a virtual address in the finalizeSymbolValues()
routine. The X86_64 target uses addAtom() function to add an object of
the GLOBAL_OFFSET_TABLEAtom class to do the same thing. What is the
reason of this difference? Is the GLOBAL_OFFSET_TABLEAtom just a
useful wrapper which eliminates the necessity to assign an address to
the atom explicitly in the finalizeSymbolValues() routine?
On Tue, Oct 22, 2013 at 12:16 AM, Shankar Easwaran
<shankare...
2013 Oct 21
2
[LLVMdev] [lld] Handle _GLOBAL_OFFSET_TABLE symbol
Hi,
What is a recommended way of handling (define, assign value)
_GLOBAL_OFFSET_TABLE symbol? It looks like Hexagon and X86_64 targets
use different API to achieve the same result.
tia,
Simon
2013 Oct 21
0
[LLVMdev] [lld] Handle _GLOBAL_OFFSET_TABLE symbol
Its a DefinedAtom whose value is set by the Target Handlers.
On 10/21/2013 3:08 PM, Simon Atanasyan wrote:
> Hi,
>
> What is a recommended way of handling (define, assign value)
> _GLOBAL_OFFSET_TABLE symbol? It looks like Hexagon and X86_64 targets
> use different API to achieve the same result.
>
> tia,
>
> Simon
> _______________________________________________
2013 Oct 21
0
[LLVMdev] LLVMdev Digest, Vol 112, Issue 56
...EsLbdM=i=UL8FKM+wdf9F-LHw at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
The Hexagon target adds new atom using the addAbsoluteAtom() functions
and then assigns a virtual address in the finalizeSymbolValues()
routine. The X86_64 target uses addAtom() function to add an object of
the GLOBAL_OFFSET_TABLEAtom class to do the same thing. What is the
reason of this difference? Is the GLOBAL_OFFSET_TABLEAtom just a
useful wrapper which eliminates the necessity to assign an address to
the atom explicitly in the finalizeSymbolValues() routine?
On Tue, Oct 22, 2013 at 12:16 AM, Shankar Easwaran
<shankare...