[RFC PATCH v3 0/5] Libffi Static Trampolines

[Anthony Green]

Madhaven,

  Thank you for your continued efforts here.

On Fri, Jan 15, 2021 at 1:47 PM <madvenka@linux.microsoft.com> wrote:

> Trampoline API
> ==============
>
> There is a lot of dynamic code out there. They all have the same security
> issue. Dynamic code can be re-written into static code provided the data
> required by the static code can be passed to it just like we pass the
> closure
> pointer to an ABI handler.
>
> So, the same trampoline functions used by libffi internally need to be
> made available to the rest of the world in the form of an API. The
> following API has been defined in this solution:
>


I need a better explanation around why this new API is required, and this
new capability isn't just an implementation detail supporting the old API.

Thanks,

AG