This ticket will track the progress of the JIT backend.
My priorities will always be completing the language and VM so the JIT backend is not something I will work on for quite some time.
The JIT backend uses a technique based on copy-and-patch. For more details about that check the release notes:
https://cyberscript.dev/0.3
If anyone is interested, this can be a nice opportunity to learn more about Cyber, Zig, LLVM, clang, performance, compilers, bytecode, machine code, and assemblers.
Right now I have setup everything that you might need in src/jit and I have faith that the methodology will continue to work.
I will most likely update the contributing.md with this but in general PR's should be first come first serve and valuing quality of the implementation. This shouldn't discourage anyone, just know what you're getting into. If anything you should be doing it for the learning experience. What you might want to know is who is currently working on it so that you can collaborate and not bump heads.
This ticket will track the progress of the JIT backend.
My priorities will always be completing the language and VM so the JIT backend is not something I will work on for quite some time.
The JIT backend uses a technique based on copy-and-patch. For more details about that check the release notes: https://cyberscript.dev/0.3
If anyone is interested, this can be a nice opportunity to learn more about Cyber, Zig, LLVM, clang, performance, compilers, bytecode, machine code, and assemblers. Right now I have setup everything that you might need in
src/jitand I have faith that the methodology will continue to work.I will most likely update the contributing.md with this but in general PR's should be first come first serve and valuing quality of the implementation. This shouldn't discourage anyone, just know what you're getting into. If anything you should be doing it for the learning experience. What you might want to know is who is currently working on it so that you can collaborate and not bump heads.