You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for this feature -- it will allow OCaml to be used an an extension language! I have two questions:
Are the results of the compilation cached somewhere? Or does the executable code only live in memory? For instance the native lisp compiler for emacs (due to be released in emacs 28.1) stores the results of compilation in a .eln file so the compilation does not need to happen afresh the next time some script needs to be evaluated
Are there some major features/fixes still planned or is this feature near its final state for 4.14?
The text was updated successfully, but these errors were encountered:
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 init_top does nothing. This will be useful for MDX.
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 to1 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: