Editing JIT
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
== JIT development in octave == | |||
This page should help interested persons which want to start hacking on the current JIT implementation in octave. It's '''NOT''' intended for octave users. | |||
Last year, thanks to Max Brister's work, an initial implement of a just-in-time compiler (JITC) in LLVM for GSoC 2012. [http://planet.octave.org/octconf2012/jit.pdf Here] is Max's OctConf 2012 presentation about his current implementation. | |||
=== | === recommended reading === | ||
* [http://en.wikipedia.org/wiki/Abstract_syntax_tree AST (Abstract Syntax Tree)] | * [http://en.wikipedia.org/wiki/Abstract_syntax_tree AST (Abstract Syntax Tree)] | ||
* [http://en.wikipedia.org/wiki/Static_single_assignment_form SSA form (Static single assignment form)] | * [http://en.wikipedia.org/wiki/Static_single_assignment_form SSA form (Static single assignment form)] | ||
Line 15: | Line 15: | ||
If the conversion fails at any stage, we give up and use the interpreter. Normally, this is done by throwing a jit_fail_exception. The reason why we can't go directly to the LLVM IR, is because Octave's AST does not contain any type information, but LLVM's IR requires it. For example, A = B+C. If B and C are matrices, this has as a drastically different meaning than if B and C are scalars. We use the current types of variables to determine the types of the rest of the variables in the loop. | If the conversion fails at any stage, we give up and use the interpreter. Normally, this is done by throwing a jit_fail_exception. The reason why we can't go directly to the LLVM IR, is because Octave's AST does not contain any type information, but LLVM's IR requires it. For example, A = B+C. If B and C are matrices, this has as a drastically different meaning than if B and C are scalars. We use the current types of variables to determine the types of the rest of the variables in the loop. | ||
=== | === source code entries === | ||
* libinterp/parse-tree/pt-eval.cc line 317 | * libinterp/parse-tree/pt-eval.cc line 317 | ||
Line 29: | Line 29: | ||
*jit-util.cc (& jit-util.h) | *jit-util.cc (& jit-util.h) | ||
I haven't gone through all parts of the code yet and | I haven't gone through all parts of the code yet and dont understand a lot of it, but my first impression is that it feels like more of a text dump. The various parts need to be seperated into different files based on functionality. The current files are a tad too big IMHO. Right now all of the jit parts are in 4 files(+4 header files) which are quite large and a lot of it has no documentaion to explain how the different parts come togeather. | ||
To be fair my impressions/opinions are that of a beginner level user and you are welcome to have a look and post your own comments. | To be fair my impressions/opinions are that of a beginner level user and you are welcome to have a look and post your own comments. | ||
[[Category:Development]] | [[Category:Development]] |