Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Expose ExecutionEngine #65

Open
NathanHowell opened this issue Jun 1, 2013 · 0 comments
Open

Expose ExecutionEngine #65

NathanHowell opened this issue Jun 1, 2013 · 0 comments

Comments

@NathanHowell
Copy link
Collaborator

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 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@NathanHowell