[PATCH] D12607: [ExecutionEngine] Add to the C API possibility to create custom SectionMemoryManager

[Jauhien Piatlicki via llvm-commits]

jauhien added a comment.

Hi Lang,

In http://reviews.llvm.org/D12607#241981, @lhames wrote:

> Hi Jauhien,
>
> I'm happy to add symbol resolution methods to the abstract C memory manager interface. The stability of SectionMemoryManager is accidental though: it's just that nobody has found time to work on it. As I said - we want to reserve the right to change that behavior in the future, so we can't expose it via the stable API.


I'll work on the support for symbol resolution methods then. But before it I want to figure out one thing that I do not understand. This thing is how APIs that I've added need SectionMemoryManager implementation to be stable.

Three facts that I rely on (memory management API, symbol resolution API, existence of some MM) will be exposed by execution engine API anyway. If some of MM methods will change implementation, client that uses it correctly will not see it, as it sees only quite common interface. Even SectionMemoryManager itself can be removed and replaced by something that implements necessary functionality. Could you, please, point me to the exact place where this patch (API, not realization) demands SectionMemoryManager to be stable?


http://reviews.llvm.org/D12607