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.

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.

Line 15:

Line 13:

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 ===

+

=== Source code entries ===

* libinterp/parse-tree/pt-eval.cc line 317

* libinterp/parse-tree/pt-eval.cc line 317

Revision as of 11:31, 5 December 2013

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. Here is Max's OctConf 2012 presentation about his current implementation.

Recommended reading

IRC snippets

JIT currently only is invoked at the start of loops. Basically, JIT works by converting Octave's AST to the LLVM Internal Representation (IR). This code is in libinterp/interp-core/pt-jit.cc. This is achieved by constructing an intermediate IR, which is used for type inference, then converting that intermediate IR to LLVM's IR.
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/octave-value/ov-usr-fcn.cc line 385

That just invokes the jit code, which you can find in pt-jit.cc

Notes by Amod Mulay(white)

The snippets above define the point in execution where the jit code is called.
All of the files for jit implementation are in libinterp/interp-core, the main files are:

pt-jit.cc (& pt-jit.h)

jit-ir.cc (& jit-ir.h)

jit-typeinfo.cc (& jit-typeinfo.h)

jit-util.cc (& jit-util.h)

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.