llvm icon indicating copy to clipboard operation
llvm copied to clipboard

Published 20 hours ago • verified publisher icon bos

Expose ExecutionEngine

Open NathanHowell opened this issue 11 years ago • 0 comments

The ExecutionEngine has been restricted to the land of FFI for quite some time. The preferred route for dealing with an ExecutionEngine has been through the EngineAccess monad. This is historically significant because LLVM previously allowed a single ExecutionEngine per process, a limit that has since been lifted. I think it's time to change this. I have an old patch 1fce8ae1593b9f48072616cf36baace2fc7c8ce7 sitting around that totally removes the EngineAccess related goo. This might be a bit extreme, so I'm wondering if anyone else here has opinions on the matter. Should we:

  • Remove EngineAccess totally and replace it's usage with ExecutionEngine (per the referenced patch)
  • Add a second set of functions to work with ExecutionEngine, and optionally mark the EngineAccess bits as deprecated.

NathanHowell avatar Jun 01 '13 19:06 NathanHowell