Displaying 3 results from an estimated 3 matches for "nbranchsizes".
2017 Jan 06
3
RFC: LLD range extension thunks
...en call sites) then it's still just a simple
dynamic programming problem, solvable in linear [1] time by trying each
branch size at the first available call site, with a cache of the minimum
cost assuming the first 0, 1, 2 .. N call sites have already been covered.
[1] or at least nCallSites * nBranchSizes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170106/e12b0316/attachment.html>
2017 Jan 06
2
RFC: LLD range extension thunks
...mple
>> dynamic programming problem, solvable in linear [1] time by trying each
>> branch size at the first available call site, with a cache of the minimum
>> cost assuming the first 0, 1, 2 .. N call sites have already been covered.
>>
>> [1] or at least nCallSites * nBranchSizes
>>
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>
>>
>
-------------- next part --------------
An HTML attachment was...
2017 Jan 05
2
RFC: LLD range extension thunks
Hello Rui,
Thanks for the comments
- Synthetic sections and rewriting relocations
I think that this would definitely be worth trying. It should remove
the need for thunks to be represented in the core data structures, and
would allow .
It would also mean that we wouldn't have to associate symbols with
thunks as the relocations would directly target the thunks. ARM
interworking makes reusing