Hiroshi Shirosaki wrote: > Recently some vim plugins use if_lua for performance issues because > Vim script is not so fast. For example Shougo's neocomplete.vim[1] > shows better performance thanks to if_lua. > > According to some benchmark results LuaJIT looks much faster than Lua > and is fully compatible to Lua 5.1.[2][3] > So that we would get more performance advantage by using LuaJIT > instead of Lua. > > On Windows just replacing Lua's dll with LuaJIT's dll in Vim directory > seems to work as expected without rebuilding vim in the case of > dynamic link. Now LuaJIT bundled vim binary for Windows is distributed > by kaoriya.[4]
Does this require renaming the .dll, thus afterwards you may forget that the file is actually the JIT one? > However linking vim with LuaJIT on Unix like OS requires some works in > configure and build process because library names and directory path > of LuaJIT are slightly different from Lua. And LuaJIT requires special > link options on Mac OS X. It might not easy for beginners. > > It would be nice if configure would prepare for LuaJIT automatically > so that users who want to use LuaJIT could easily build Vim with > LuaJIT. > > For this purpose I added a new configure option `--with-luajit`. > Here is a patch. This changes only configure. > > https://gist.github.com/shirosaki/5663617/ > > When adding `--enable-luainterp --with-luajit` as configure option, > configure tries to use LuaJIT instead of Lua . > Just with `--enable-luainterp` (without --with-luajit) configure tries > to use Lua as before. What you say hints that the JIT one is always better. So why not use luajit when it's available, falling back to non-JIT when it's not? Then it would work well for people who don't even know about the option. Right? The option might still be useful to force using one or the other. Perhaps the JIT version is released a bit later? > In addition I fixed an issue that build with > `--enable-luainterp=dynamic` doesn't work properly with Lua on Mac OS > X since shared library extension on Mac OS X is *.dylib while *.so on > Linux. > > Some vim users in Japan are interested in this fix and testing.[5] > I've tested this on Mac OS X, Ubuntu 13.04 and CentOS 6.4 with latest > vim 7.3 and it seems to work. > > > Install instructions with LuaJIT: > > Ubuntu: > $ sudo apt-get install luajit libluajit-5.1 > $ cd vim_source_directory > $ curl https://gist.github.com/shirosaki/5663617/raw | patch -p1 > $ ./configure --with-features=huge --enable-luainterp --with-luajit > $ make > $ sudo make install > > Mac OS X with Homebrew: > $ brew install luajit > $ cd vim_source_directory > $ curl https://gist.github.com/shirosaki/5663617/raw | patch -p1 > $ ./configure --with-features=huge --enable-luainterp --with-luajit > --with-lua-prefix=/usr/local > $ make > $ sudo make install > > > [1] https://github.com/Shougo/neocomplete.vim > [2] http://luajit.org/luajit.html > [3] https://github.com/vim-jp/issues/issues/48#issuecomment-15355516 > [4] http://www.kaoriya.net/news/2013/05/19/ > [5] https://github.com/vim-jp/issues/issues/348 > > > Thanks, > Hiroshi Shirosaki -- hundred-and-one symptoms of being an internet addict: 180. You maintain more than six e-mail addresses. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
