Displaying 2 results from an estimated 2 matches for "grobalobject".
Did you mean:
globalobject
2015 Dec 23
2
RFC: __attribute__((ifunc("resolver")) representation in LLVM IR
If changing nothing else I would probably go with another list since
that is what is done for functions/variables/aliases.
Having said that, more than once I wished we had an easy way to
iterate all GlobalValues or all GrobalObjects. Any thoughts on the
tradeoff having a single list with pointer to the start of each sub
list? Something like
Func1 <-> Func2 <-> Var1 <-> Var2 <-> Alias1 <-> Alias2 <-> IFunc1 <-> Ifunc2
and keep FirstFunc, FirstVar, FirstAlias and FirstIFunc pointers....
2015 Dec 21
2
RFC: __attribute__((ifunc("resolver")) representation in LLVM IR
I would like to support __attribute__((target)) later so ifunc won't be opaque
for compiler generated dispatchers.
Thank you all for the feedback!
On Sat, Dec 19, 2015 at 8:49 AM, Eric Christopher via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> I think 2 is the only reasonable answer. And to answer Reid's comment:
> yes, it might be nice if we could look through it for