[PATCH] D17934: [ELF] Implement infrastructure for thunk code creation

[Rui Ueyama via llvm-commits]

This is just an idea and I'm not suggesting that that is better, but you
can scan a list of input sections and insert stub sections to the list,
instead of appending stub sections to input/output sections.

On Mon, Mar 7, 2016 at 12:11 PM, Simon Atanasyan <simon at atanasyan.com>
wrote:

> atanasyan added a comment.
>
> In http://reviews.llvm.org/D17934#369150, @ruiu wrote:
>
> > I'm still reading this patch, but does it work for all cases? When you
> want to create a thunk for a short-range jump instruction, you want to
> locate that thunk within the range of the instruction. Output sections can
> be large. Putting thunks at end of each output section will work?
>
>
> I had a solution which puts stubs in the beginning of the corresponding
> input section. In that case the risk to get too long jump is smaller. But
> this solution seemed to me over-complicated a bit. Let me think again till
> tomorrow. Maybe I revert that solution.
>
>
> Repository:
>   rL LLVM
>
> http://reviews.llvm.org/D17934
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20160307/37020ff6/attachment.html>