Re: [ANN] CLX - Ahead-of-Time Lua 5.5 Compiler

Thank you for the questions.

   1. 
   
   The GC is a custom implementation. It's an incremental mark-and-sweep 
   collector designed specifically for CLX's runtime.
   2. 
   
   Garbage collection is per LState, not shared globally. "Stop the world" 
   therefore only applies to the state being collected, not to all application 
   threads. Native threads can/should run independent states concurrently.
   3. 
   
   Regarding dynamic Lua code, CLX currently takes a strict AOT approach. 
   The current focus is on statically compiled Lua applications rather than 
   interpreter/dynamic execution model (maybe in the future ?)
   

Le mercredi 24 juin 2026 à 13:57:25 UTC+2, Viacheslav Usov a écrit :

> On Sun, Jun 21, 2026 at 5:17 PM <[email protected]> wrote:
>
> > CLX is a new open-source ahead-of-time compiler for Lua 5.5.
> > CLX compiles Lua source code to standalone native executables through 
> modern C++20 toolchains (Clang, GCC, and MSVC).
>
> Hi, some questions which I could not find good answers for yet.
>
> 1. GC. Is it based on some well known project? If so, could you
> reference that? If not, well, where is its code?
> 2. Native multithreading. The original Lua VM ignores native OS
> threads and keeps everything, including GC, in a Lua state. If
> somebody wants to run a Lua state on multiple native threads it is
> their problem. What about CLX? In particular, is GC shared or also per
> state? What does "stop the world" mean then?
> 3. What is the strategic plan for dynamic Lua code?
>
> Cheers,
> V.
>

-- 
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/04ae5a1a-0dc6-45ad-b1c1-d91a679d762en%40googlegroups.com.