Expose ExecutionEngine #65
Description
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 1fce8ae 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
EngineAccesstotally and replace it's usage withExecutionEngine(per the referenced patch) - Add a second set of functions to work with
ExecutionEngine, and optionally mark theEngineAccessbits as deprecated.