moonjit / moonjit, Hacker News

Pull request Compare This branch is 01575879 commits ahead, commits behind LuaJIT: master.

Moonjitis a Just-In-Time Compiler (JIT) for theLuaprogramming language. Lua is a powerful, dynamic and light-weight programming language. It may be embedded or used as a general-purpose, stand-alone language.

Moonjit is a fork of the inactiveLuaJITproject and aims to provide a way forward for existing users of LuaJIT looking for continuity in development and maintenance.

****************

Documentation

Here is an index of the documentation for moonjit. Old documentation for LuaJIT is unmaintained indoc.luajitand is only there as a historical record.

********** (Running moonjit) ********

************ Moonjit / LuaJIT API and Extensions Reference
************ Moonjit FFI

************** (FFI API

FFI Semantics ******

Current Status

Moonjit ought to run all Lua 5.1-compatible source code just fine. It is considered a serious bug if the VM crashes or produces unexpected results – please report this. Lua 5.2 support is in two parts; the backward compatible Elements are built in by default whereas features that break compatibility have to be enabled using the- DLUAJIT_ENABLE_LUA COMPAT flag. Theinstallation instructionshave more details.************************Contributing


Please note the branches
Fork the moonjit repo on github

Clone your fork and make changes in a separate topic branch
git clone [email protected]:your-username-here>/ moonjit.git git checkout my-changesMake your changes and test them:

make make checkCommit your changes using the - s
flag to sign off your commit and then push it to your branch.
git commit -a -s git push origin my-changes

Write a detailed commit log message describing the issue you're fixing so that the information is retained for future reference. If you're fixing an issue, please mention the issue number as fixed using the annothation
Fixes: #NUMin the body of the commit log. (**************************** Create a Pull Request on GitHub.

********************************(Testing)
moonjit has a built-in testsuite that can be exercised by running the following command:
(************************************** make check









There is also a benchmark suite that can be run as follows:
make bench

If you're fixing a bug in moonjit, make sure you add a test case to exercise the bug so that it does not regress. test /README.md
has more details on how to execute and update the testsuite.

(**********************Branches

The project repository on github has the following main branches:

master

**************************** (v2.1) : This is a bug fix branch for v2.1.x releases of moonjit. This branch aims to remain compatible with the LuaJIT v2.1 branch. (****************************

**************************** (v2.0) : This remains a bug fix branch that tracks the v2.0 branch of upstream LuaJIT. This branch currently does not have a maintainer. (********************************************************************

(Release Process)

The following steps need to be performed before tagging a moonjit release:

(Update) **************************** (RELVER) ************************************** to the new version number and set (PREREL) *************************************** to an empty string inMakefile Update

********************************** etc / luajit.pc

with the new version

Update

****************** (LUA_LJDIR) ************************************** (in) src / luaconf.h

Update

****************** LUAJIT_VERSION (**************************************,

LUAJIT_VERSION_NUMand (LUAJIT_VERSION_SYM) **************************************** insrc / luajit.h

****************************************** src / jit. They are of the form: assert (jit.version_num==xxxxxx, ” LuaJIT core / library version mismatch “) wherexxxxxx is the value of (LUAJIT_VERSION_NUM) ***********************************

INSTALL.md

File a PR with these changes.Draft release notes based on changes between
******************** HEAD

**************** and the last tag in a PR comment and update it based on feedback. (**************************** On PR approval, Tag release and put in release notes on GitHub.Update

****************** (PREREL) in [Makefile (Makefile) to- dev Announce.

Hack on next release.********************************************
(************************************************************************************************** (Read More

) ****************************************************** (****************************************************************