Displaying 3 results from an estimated 3 matches for "pltentrywould".
2020 Aug 21
2
[RFC][LLVM] New Constant type for representing function PLT entries
...uld be analogous to BlockAddress, but
>> instead represent the PLT entry for functions. The usage
>> could look something like:
>>
>> pltentry(@function)
>>
>> and would always have the same type as the function. A
>> pltentrywould operate exactly like a function, but the main
>> difference is that it’s lowered to the PLT entry
>> (function at plt) on targets that support PLT relocations. The
>> linker can then decide if it should be relaxed into a direct
>> reference or...
2020 Aug 20
4
[RFC][LLVM] New Constant type for representing function PLT entries
Hi all,
We would like to propose a new Constant type in LLVM for representing
entries in the Procedure Linkage Table (PLT).
The PLT is a data structure used for dispatching position-independent
function calls to appropriate functions where the address of the function
is not known statically. Right now, if a call is made to a function, it may
be lowered to a direct call to the function itself or
2020 Aug 21
5
[RFC][LLVM] New Constant type for representing function PLT entries
I do have concerns about the amount of object level modeling that we want
to do in the IR though. While it isn't the highest level IR we've managed
to mostly avoid these kinds of features/complications in the past. I'm
definitely interested in hearing some alternate implementations here and
there rather than a full set of constants for relocations. Keeping the IR
abstract enough over