On 8/24/2013 2:25 AM, Marco Patzer wrote:
On 2013–08–24 Hans Hagen wrote:

Hard to say what is the issue but it is not a luajittex issue. We
don't do anything special, for instance jit is turned off because
there is no gain at all (actually with jit enabled, the run is
slower).

I can confirm that. I did not find a real-world document which
compiled faster with jit. Using the virtual machine provides between
8% and 25% speed gain here.

there is a bit more to gain otherwise (luigi and i will talk about speed related issues at the context meeting)

There is however one difference and that is the compiled lua code:
lua and luajit have incompatible formats (apart from the fact that
luatex is 5.2 and luajittex is 5.1++). Normally compilation happens
automatically i.e. when a font is loaded by luatex, context will
generate the relevant compiled file when luajittex is used.

One possibility is that there is some mismatch in version numbers
that gets unnoticed.

Let me know if I can provide any additional info.

ok, but currently i have no clue

(it might be that there has been a fix without jumping the internal otf handler version number, in which case a mismatch can go unnoticed and no recompile happens in the jit variant)

Hans


-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
    tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : [email protected] / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Reply via email to