MAD-NG.docs
LjTools
MAD-NG.docs | LjTools | |
---|---|---|
3 | 11 | |
37 | 251 | |
- | - | |
5.8 | 0.0 | |
4 months ago | over 1 year ago | |
TeX | C++ | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
MAD-NG.docs
-
Bytecode for a Register Machine
Did you have a look at LuaJIT? See e.g. http://luajit.org/, http://wiki.luajit.org/Bytecode-2.0, http://wiki.luajit.org/SSA-IR-2.0, and https://github.com/MethodicalAcceleratorDesign/MADdocs/blob/master/luajit/luajit-doc.pdf
-
Tracing JITs and coverage-guided fuzzers
It doesn't know that it's an interpreter loop; it just makes a hotpath analysis and then makes decisions on what (variable lenght) traces to optimize and compile. Have a look at https://github.com/MethodicalAcceleratorDesign/MADdocs/blob/master/luajit/luajit-doc.pdf. Actually I'm just a LuaJIT user, not a specialist for tracing JITs. I just wanted to correct the wrong statement that "performance improvements for tracing JITs" "struggle to achieve their goals" with "Interpreters and similar programs that “look like” interpreters". If that was the case, PyPy would not be successful and I wasn't able to achieve the measured speed-up (which btw is higher than the speed-up measured at http://luajit.org/performance_x86.html).
LjTools
-
LuaJIT decompiler that supports GOTO statements?
I dug a little more and came across this tool which does seem to have the capability to view all LuaJIT Bytecode. https://github.com/rochus-keller/LjTools
-
A History of Lua
> a large lua game code base, over 4000 files, 1.5 million lines of code
Interesting; how do you manage to keep consistency? Do you have special tools to e.g. detect inadvertent global variables? I once wrote a Smalltalk VM in Lua (https://github.com/rochus-keller/Smalltalk/blob/master/Inter...) which is a much smaller code base but even with this size I quickly would have lost track of e.g. scopes and names without tools I had to write myself (https://github.com/rochus-keller/LJTools).
- Minimalism in Programming Language Design
-
KT/COBOL — Choosing a VM edition — I need to hear your experiences with the VM you're currently using for your project.
Most of my languages have VM backends; see e.g. https://github.com/rochus-keller/Oberon; I implemented different backends generating LuaJIT bytecode; a year ago I switched to Mono which is based on ECMA-335; here is a discussion why I switched: https://github.com/rochus-keller/Oberon/releases/tag/IDEv0.9.0; I implemented utility libraries for both LuaJIT and CIL bytecode; see https://github.com/rochus-keller/LjTools/, https://github.com/rochus-keller/Pelib/ and https://github.com/rochus-keller/MonoTools/. I evaluated many VMs and think the mentioned ones are best suited. There were a lot of challenges with both technologies, what is to be expected, and too much to describe here.
-
LuaJIT for backend?
LuaJIT is well suited as a backend/runtime environment for custom languages; I did it several times (see e.g. https://github.com/rochus-keller/Smalltalk, https://github.com/rochus-keller/Som/, https://github.com/rochus-keller/Oberon/). I also implemented a bit of infrastructure to ease the reuse: https://github.com/rochus-keller/LjTools. LuaJIT has some limitations though; if you require closures you have to know that the corresponding LuaJIT FNEW bytecode is not yet supported by the JIT, i.e. switches to the interpreter; as a work-around I implemented my own closures; LuaJIT also doesn't support multi-threading, but co-routines; and there is no debugger, and the infrastructure to implement one has limitations (i.e. performance is low when running to breakpoints). For most of my projects this was no issue. Recently I switched to CIL/Mono for my Oberon+ implementation which was a good move. But still I consider LuaJIT a good choice if you can cope with the mentioned limitations. The major advantage of LuaJIT is the small footprint and impressive performance for dynamic languages.
-
Writing a Register Based VM
Implementing a VM is certainly interesting, but if you just need a fast backend you could generate LuaJIT bytecode (see e.g. https://github.com/rochus-keller/ljtools/ LuaJitComposer.h/cpp).
- Finl Is Not LaTeX
- (LuaJIT) How to directly modify strings within LuaJIT Bytecode?
-
Bytecode for a Register Machine
If you want to re-use LuaJIT as a backend, have e.g. a look at https://github.com/rochus-keller/ljtools
-
Favorite Program for writing LUA?
Recently I mostly use https://github.com/rochus-keller/LjTools#lua-parser-and-ide-features
What are some alternatives?
ubpf - Userspace eBPF VM
SATySFi - A statically-typed, functional typesetting system
Smalltalk - Parser, code model, interpreter and navigable browser for the original Xerox Smalltalk-80 v2 sources and virtual image file
wasmtime - A fast and secure runtime for WebAssembly
Oberon - Oberon parser, code model & browser, compiler and IDE with debugger
langs
port70 - A Gopher server in Lua
tex-rs - A port of TeX82 to Rust. (WIP)
LuaJIT - Mirror of the LuaJIT git repository
tl - The compiler for Teal, a typed dialect of Lua