-
Notifications
You must be signed in to change notification settings - Fork 8
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
[Questions] Caching of compilation and project status #4
Comments
Thanks for your interest! No caching is done at the moment but that should be fairly easy to add. There are no major feature or changes planned. Most of the fixes we'd lke are actually fixes to the native toplevel rather than the JIT itself. What remains for the release is a bit of polish, notably making sure one can write native and bytecode compatible code, including if they use the JIT. That means shipping a bytecode version of the JIT where |
BTW I noticed PR 776: Allow Dynlink only on Domain 0 being merged to the 5.00 branch on the multicore repo. Does this mean that ocaml-jit could now work against the multicore branch? BTW, I tried to do this myself by cherry-picking commits into the 5.00 branch from:
While I was able to able to cherry-pick the commits, I was not able to get the compiler to build. Either I forgot a commit or this task is non-trivial. Here is where my compiler compilation failed: File "/home/abc123/latest-multicore/ocaml-multicore/toplevel/native/topeval.ml", line 56, characters 13-23:
56 | Lprim (Pfield pos,
^^^^^^^^^^
Error: The constructor Pfield expects 3 argument(s),
but is applied here to 1 argument(s) |
Thanks for this feature -- it will allow OCaml to be used an an extension language! I have two questions:
.eln
file so the compilation does not need to happen afresh the next time some script needs to be evaluatedThe text was updated successfully, but these errors were encountered: