Som
mir
Som | mir | |
---|---|---|
8 | 19 | |
22 | 2,187 | |
- | - | |
0.0 | 7.7 | |
over 1 year ago | 23 days ago | |
C++ | C | |
GNU General Public License v3.0 only | MIT License |
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.
Som
-
Making Smalltalk on a Raspberry Pi (2020)
> Smalltalkish
Have a look at the SOM dialect which is successfully used in education: http://som-st.github.io/
Here is an implementation in C++ which runs on LuaJIT: https://github.com/rochus-keller/Som/
> unfortunately out of print book Smalltalk 80: the language and its implementation is commonly recommended
I assume you know this link: http://stephane.ducasse.free.fr/FreeBooks/BlueBook/Bluebook....
Here is an implementation in C++ and Lua: https://github.com/rochus-keller/Smalltalk
- Do transpilers just use a lot of string manipulation and concatenation to output the target language?
-
Ask HN: Admittedly Useless Side Projects?
- https://github.com/rochus-keller/Smalltalk/ Parser, code model, interpreter and navigable browser for the original Xerox Smalltalk-80 v2 sources and virtual image file
- https://github.com/rochus-keller/Som/ Parser, code model, navigable browser and VM for the SOM Smalltalk dialect
- https://github.com/rochus-keller/Simula A Simula 67 parser written in C++ and Qt
> do you regret those endeavours?
No, not in any way; the projects were very entertaining and gave me interesting insights.
-
Ask HN: Recommendation for general purpose JIT compiler
If your DSL is statically typed then I recommend that you have a look at the Mono CLR; it's compatible with the ECMA-335 standard and the IR (CIL) is well documented, even with secondary literature.
If your DSL is dynamically typed I recommend LuaJIT; the bytecode is lean and documented (not as good as CIL though). LuaJIT also works well with statically typed languages, but Mono is faster in the latter case. Even if it was originally built for Lua any compiler can generate LuaJIT bytecode.
Both approaches are lean (Mono about 8 MB, LuaJIT about 1 MB), general purpose, available on many platforms and work well (see e.g. https://github.com/rochus-keller/Oberon/ and https://github.com/rochus-keller/Som/).
-
When is Smalltalk's speed an issue?
At the latest when you run a benchmark suite like Are-we-fast-yet; here are some measurment results: http://software.rochus-keller.info/are-we-fast-yet_crystal_lua_node_som_pharo_i386_results_2020-12-29.pdf. See also https://github.com/rochus-keller/Som/ and https://github.com/rochus-keller/Smalltalk.
-
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.
-
Optimizing an old interpreted language: where to begin?
One option is to leverage someone else's JIT: you could, for example, rewrite the interpreter to transpile to Lua source, which is then run in LuaJIT. There's a Smalltalk dialect which does this successfully; the Lua version runs in 1/12th the time of the C interpreted version. https://github.com/rochus-keller/Som You can use LuaJIT's FFI to call back into the Stunt server, or else just rewrite it completely in Lua --- large parts of the Stunt server will just go away in a native Lua implementation (e.g. the object database is just a table). Javascript would be another candidate for this.
-
JITted lang which is faster than C?
This is a completely different kind of measurement; unfortunately this is not clear enough from my Readme. I wanted to find out, how well my naive Bluebook interpreter performs on LuaJIT (using my virtual meta tracing approach) compared to Cog, which is a dedicatd Smalltalk VM optimized with whatever genious approaches over two decades (or even longer considering the long experience record by Elliot). This experiment continues in https://github.com/rochus-keller/Som, because I didn't want to modify the original Smalltalk image. I found that my naive LuaJIT based approach is about factor seven behind the highly optimized Cog/Spur, and further improvements would require similar optimization tricks as in the latter.
mir
-
Ravi is a dialect of Lua, with JIT and AOT compilers
MIR comes from the Rubyverse and isn't related to LLVM MLIR.
https://github.com/vnmakarov/mir?tab=readme-ov-file#mir
- Mir: Strongly typed IR to implement fast and lightweight interpreters and JITs
- Implementing Interactive Languages
- I developed a faster Ruby interpreter
-
Are Hoistings Possible for C++?
When you say a fork of LLVM, am I correct in assuming that you specifically mean a fork of Clang? I don't see how the compiler backend would affect support for language extensions, regardless of whether it's an exception to that such as Tcc, Cproc, the MIR C jitter, lacc, 8cc, 9cc, and chibicc. Most of those are not for production, excluding Cproc and Tcc (at least according to Suckless or Oasis).
-
Suggestion for a backend?
MIR
- Ask HN: Recommendation for general purpose JIT compiler
- How to learn compilers: LLVM Edition
- What instructions are needed for a language vm
-
Nelua Programming Language
> I wish C was scriptable
C kinda can be used as scripting language with MIR project https://github.com/vnmakarov/mir
It was released just a few days ago, and I've successfully use it as an alternative and fast C compiler with Nelua.
What are some alternatives?
Smalltalk - Parser, code model, interpreter and navigable browser for the original Xerox Smalltalk-80 v2 sources and virtual image file
asmjit - Low-latency machine code generation
rockstar - Makes you a Rockstar C++ Programmer in 2 minutes
LuaJIT - Mirror of the LuaJIT git repository
qbe-rs - QBE IR in natural Rust data structures
Cwerg - The best C-like language that can be implemented in 10kLOC.
ubpf - Userspace eBPF VM
ecl
sljit - Platform independent low-level JIT compiler
kcs - Scripting in C with JIT(x64)/VM.
Oberon - Oberon parser, code model & browser, compiler and IDE with debugger
terra - Terra is a low-level system programming language that is embedded in and meta-programmed by the Lua programming language.