-
Notifications
You must be signed in to change notification settings - Fork 99
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.
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
Update Kaleidoscope Chapters 3, 4 and 5 to use OrcJIT #1
Comments
mjsabby
added a commit
that referenced
this issue
Apr 30, 2015
mjsabby
added a commit
that referenced
this issue
Apr 30, 2015
# The first commit's message is: Add DIBuilder Bindings, need to also add C++ code as part of LLVMSharp build # This is the 2nd commit message: Add DIBuilder Bindings, need to also add C++ code as part of LLVMSharp build Revert "Add DIBuilder Bindings, need to also add C++ code as part of LLVMSharp build" This reverts commit 431008c. Add DIBuilder Bindings #1 (CSharp side)
mjsabby
added a commit
that referenced
this issue
Apr 30, 2015
…p build Add DIBuilder Bindings, need to also add C++ code as part of LLVMSharp build Revert "Add DIBuilder Bindings, need to also add C++ code as part of LLVMSharp build" This reverts commit 431008c. Add DIBuilder Bindings #1 (CSharp side) Revert "Add DIBuilder Bindings, need to also add C++ code as part of LLVMSharp build" This reverts commit 431008c.
I suppose we can skip over MCJIT and move to OrcJIT now that it looks like C API support is around the horizon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since JIT is no longer available in LLVM 3.6, moving to MCJIT is essential as folks try to run the tutorial and find that it's mysteriously broken.
The text was updated successfully, but these errors were encountered: