Re: [ANN] clx 0.3.0 released

[email protected]
Newsgroups gmane.comp.lang.lua.general
Message-ID <[email protected]>
Hi Rodion,

Thanks for the question.

The goal of clx is mainly to provide a modern  compilation path for Lua 
5.5, producing small standalone native executables. I wouldn't consider 
it a direct replacement for LuaJIT, since the target (Lua 5.1) and 
approaches are quite different (LuaJIT still uses an interpreter and 
dépends on lua51 Dynamic library).

And yes, you're correct: when using dynamically loaded code, it runs 
through the optional embedded Lua 5.5 VM, so its performance is that of 
the interpreter (minus the bridge overhead). The main application code 
remains compiled native code and interfaces with dynamic code 
seamlessly.

Regards,

Samir

Le 23/08/2026 22:15, Родион Горковенко a écrit :

> Samir, Hi!
> 
> May I ask about your perceived "strategic goal"? I.e. do you aim to 
> create replacement for LuaJIT (given that it drags behind the language 
> standard) or is it for now just a project mainly driven by developer's 
> curiosity?
> 
> As I understand CLX doesn't provide JIT behavior, so if some code is 
> loaded and executed dynamically its performance should be that of 
> typical "interpreted" code, not matched to native / JIT execution?
> 
> thanks in advance,
> sincerely yours,
> Rodion
> 
> On Sat, Aug 22, 2026 at 12:21 PM Samir Tine <[email protected]> 
> wrote:
> 
>> Hi,
>> 
>> clx is an open-source ahead-of-time (AOT) compiler that turns Lua 
>> programs into standalone native executables. Version 0.3.0 has now 
>> been released, with support for Linux, Windows, and macOS.
>> 
>> The main new feature is an optional embedded Lua 5.5 VM with a native 
>> bridge, enabling dynamic code execution through load(), loadfile(), 
>> and dofile() while seamlessly interacting with AOT-compiled code.
>> 
>> The VM is only included when requested with the --dynamic flag, so 
>> applications that don't need dynamic loading retain a minimal 
>> executable size and runtime footprint.
>> 
>> Compatibility has also improved significantly, with popular Lua 
>> libraries such as dkjson, serpent, middleclass, and lume now compiling 
>> and running out of the box.
>> 
>> This release also brings numerous optimizations, including native 
>> int64 code generation, escape-analysis-driven arena allocation, 
>> per-table inline caches, SIMD optimizations, faster coroutine 
>> switching, improved Lua 5.5 compatibility, and various runtime 
>> improvements. clx now matches or outperforms LuaJIT on several 
>> benchmark workloads.
>> 
>> https://samyeyo.github.io/clx
>> 
>> Regards,
>> 
>> Samir Tine
>> 
>> --
>> You received this message because you are subscribed to the Google 
>> Groups "lua-l" group.
>> To unsubscribe from this group and stop receiving emails from it, send 
>> an email to [email protected].
>> To view this discussion visit 
>> https://groups.google.com/d/msgid/lua-l/aa3dce3a-7c11-401c-95d0-611a8385552en%40googlegroups.com 
>> [1].
> 
> --
> You received this message because you are subscribed to the Google 
> Groups "lua-l" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to [email protected].
> To view this discussion visit 
> https://groups.google.com/d/msgid/lua-l/CAL2n1txE45GT9UNKBAZ3ZGuveFMgdA9OejnHH3Y19M8tBuqibQ%40mail.gmail.com 
> [2].


Links:
------
[1] 
https://groups.google.com/d/msgid/lua-l/aa3dce3a-7c11-401c-95d0-611a8385552en%40googlegroups.com?utm_medium=email&utm_source=footer
[2] 
https://groups.google.com/d/msgid/lua-l/CAL2n1txE45GT9UNKBAZ3ZGuveFMgdA9OejnHH3Y19M8tBuqibQ%40mail.gmail.com?utm_medium=email&utm_source=footer

-- 
You received this message because you are subscribed to the Google Groups "lua-l" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion visit https://groups.google.com/d/msgid/lua-l/e7baed0bfde3f5f38dbddd75b84715f7%40luart.org.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.