The world-class script munging capabilities and rapid prototyping capabilities of C, combined with the durable performance of your favorite scripting language. A match made in heaven for operational scripts
> What's different between tcc -run and CJIT?
>The main difference is in usability.
> CJIT improves three main UX aspects for now:
> It works as a single executable file which embeds the TinyCC compiler, all its headers and its standard library. This way there is no need to install anything system wide, check paths and setup build folders.
> It supports adding multiple files into one execution: can accept wildcards to ingest anything that is a C source, a pre-compiled object or a shared library. The symbols exported by each file will be visible to all during the same execution.
> It finds automatically common system libraries for each target platform, avoiding the need to repeat these settings and look for the right paths.
It's inspired by Terry Davis who didn't believe in sandboxes and security, he wanted to just run code and write code. It's your responsibility to read the code, :-P
Looks interesting and fun, but in no instance of any C compiler I've come across is the "classic example" of "hello, world" using `fprintf(stderr, ...)`
Julia uses a model similar to this. The main advantage is that you can interact much more easily if you have a REPL running where you can do things (assign variables load data etc) and then define/try out new code on that data.
This model traces back to Lisp and how BASIC was originally designed at Dartmouth (the pure interpreter approach was a solution to fit it into 8 bit home computers).
The best tooling approach is a mix of interpreter, dynamic and ahead of time compilers, it is a pity that not all toolchains provide this.
I wonder whether CJiT can compile itself a-la GCC and LLVM.
FAQs don't mention this and maybe the next weekend I will try to boot cjit with cjit itself.
Agreed, how HolyC serves as an inspiration could be clarified. Was it an aspect of HolyC? The background/context of the author's life, meaning Terry Davis was inspirational? Impossible to tell. Other resources [0] [1] don't mention this aspect.
I’m not surprised by it, but I am confused as I do not see anything that reminds me of TempleOS, HolyC, or Davis. If anything, this is just pushing the tcc —run functionality one step further.
The source for the site is here: https://github.com/dyne/cjit/tree/main/docs. It's a VitePress site with a custom theme. Glancing through the code, I don't see any obvious signs of LLM coding. It also definitely wasn't created with Codex specifically, because according to the commit history, the first version of the site was in late 2024, months before Codex even released.
> Be welcome to the exciting world of graphical C applications using SDL (Simple DirectMedia Layer). SDL, originally developed by Sam Lantinga in 1998...
For the uninitiated who didn't watch Terry's streams, HolyC is both an AOT and JIT language, but the JIT was in some ways much more rudimentary and in some ways much more powerful than a typical JIT compiler. Like this CJIT project, it basically could dynamically link and compile source code, spit the assembly into memory and proceed to immediately execute it. In fact, the system shell was literally JIT compiled HolyC. Which also meant you can do fun things like call kernel functions directly from the command line.
Related:
Show HN: CJIT, a single-binary C compiler that can self host - https://news.ycombinator.com/item?id=47751458 - April 2026 (1 comment)
C, Just in Time - https://news.ycombinator.com/item?id=42246209 - Nov 2024 (7 comments)
(Pity the Show HN didn't get attention - we'll email the author)
hi! matter of timing I guess, development isn't stopping :^) a friend just prompted me to look at unx - fun to see if it all works with cjit
Pair this with Fil-C(https://fil-c.org/) and now you have C but as a truly bonafide scripting language.
The world-class script munging capabilities and rapid prototyping capabilities of C, combined with the durable performance of your favorite scripting language. A match made in heaven for operational scripts
Which sounds a lot like the worst of all worlds.
Party pooper.
[dead]
Cool idea.
I was wondering why the release explicitly is `cjit-x86_64-ubuntu-24.04` instead of generic linux, but it does in fact appear to not work on Arch:
`tcc: error: file '/lib/x86_64-linux-gnu/libgcc_s.so.1' not found`
I'm guessing that's due to a `dlopen` since it's not listed by `ldd`
The TUI demos work great, but I couldn't get the SDL examples to resolve all the missing symbols after trying for a bit.
> What's different between tcc -run and CJIT? >The main difference is in usability.
> CJIT improves three main UX aspects for now:
> It works as a single executable file which embeds the TinyCC compiler, all its headers and its standard library. This way there is no need to install anything system wide, check paths and setup build folders.
> It supports adding multiple files into one execution: can accept wildcards to ingest anything that is a C source, a pre-compiled object or a shared library. The symbols exported by each file will be visible to all during the same execution.
> It finds automatically common system libraries for each target platform, avoiding the need to repeat these settings and look for the right paths.
That read like a supply-chain attack gold mine if you ask me.
It's inspired by Terry Davis who didn't believe in sandboxes and security, he wanted to just run code and write code. It's your responsibility to read the code, :-P
Looks interesting and fun, but in no instance of any C compiler I've come across is the "classic example" of "hello, world" using `fprintf(stderr, ...)`
To each their own I guess.
I give you `if (0 > fdprintf (STDERR_FILENO, ...))` instead.
But on a serious matter, it's a good thing to tell a beginner that diagnostics belong on stderr, not stdout.
Give io buffering an inch and it will take a mile
The real classic is from The C Programming Language (where I saw it) and is:
main( ) { printf("hello, world"); }
Much more interesting is Mir: https://github.com/vnmakarov/mir
It has all the tools for custom JIT including a nice C compiler.
rcc[1] is another real-JIT C compiler. antcc[2] and xcc[3] are worth mentioning for being fast-enough to run C like scripting.
[1] https://github.com/dstogov/rcc
[2] https://codeberg.org/lsof/antcc
[3] https://github.com/tyfkda/xcc
> CJIT is not a tracing or adaptive JIT in the VM sense. It does not interpret first and optimize hot paths later.
> CJIT uses TinyCC to compile C quickly, often in memory, and can execute the resulting code immediately.
Wait, what's the difference between this and just using tinycc directly?
Happy to be proven wrong here, since the project has been around for a couple years. It doesn't appear to just be a random AI one-shot thing.Julia uses a model similar to this. The main advantage is that you can interact much more easily if you have a REPL running where you can do things (assign variables load data etc) and then define/try out new code on that data.
This model traces back to Lisp and how BASIC was originally designed at Dartmouth (the pure interpreter approach was a solution to fit it into 8 bit home computers).
The best tooling approach is a mix of interpreter, dynamic and ahead of time compilers, it is a pity that not all toolchains provide this.
You may be disappointed by the FAQ then https://dyne.org/cjit/faq.html (other than it really isn't an AI thing).
I wonder whether CJiT can compile itself a-la GCC and LLVM. FAQs don't mention this and maybe the next weekend I will try to boot cjit with cjit itself.
> inspired by HolyC by Terry Davis
Definitely was not expecting this reference.
https://en.wikipedia.org/wiki/TempleOS#HolyC
https://en.wikipedia.org/wiki/Terry_A._Davis
> Definitely was not expecting this reference.
Agreed, how HolyC serves as an inspiration could be clarified. Was it an aspect of HolyC? The background/context of the author's life, meaning Terry Davis was inspirational? Impossible to tell. Other resources [0] [1] don't mention this aspect.
[0] https://www.theregister.com/2024/11/16/rusthaters_unite_filc...
[1] https://github.com/pizlonator/fil-c/blob/deluge/README.md
I’m not surprised by it, but I am confused as I do not see anything that reminds me of TempleOS, HolyC, or Davis. If anything, this is just pushing the tcc —run functionality one step further.
probably because the shell on TempleOS is actually a HolyC REPL, and HolyC is JIT compiled.
Did you use Codex 5.4 for the web design? :p I think Codex tends to do very similar designs, could be completely mistaken tho
The source for the site is here: https://github.com/dyne/cjit/tree/main/docs. It's a VitePress site with a custom theme. Glancing through the code, I don't see any obvious signs of LLM coding. It also definitely wasn't created with Codex specifically, because according to the commit history, the first version of the site was in late 2024, months before Codex even released.
Looks like a generic static site generator page to me. I'd be surprised if dyne folks used a closed system like Codex specifically.
You should release a static version of it.
Sweet project! I will give this a go today :)
The site visually feels "compressed" due to the font used? It's a bit jarring. The tutorial link in the header nav doesn't go anywhere.
It goes to https://dyne.org/cjit/tutorial.html for me, and very much works as I would expect it to (chromium engine browser, MacOS)
Inspired by Terry. But does it glow?
https://dyne.org/cjit/graphics.html#cjit-for-graphical-appli...
> Be welcome to the exciting world of graphical C applications using SDL (Simple DirectMedia Layer). SDL, originally developed by Sam Lantinga in 1998...
That's batteries included.
It links to the system SDL, on Linux at least.
> inspired by HolyC by Terry Davis
...in what way? o.O
For the uninitiated who didn't watch Terry's streams, HolyC is both an AOT and JIT language, but the JIT was in some ways much more rudimentary and in some ways much more powerful than a typical JIT compiler. Like this CJIT project, it basically could dynamically link and compile source code, spit the assembly into memory and proceed to immediately execute it. In fact, the system shell was literally JIT compiled HolyC. Which also meant you can do fun things like call kernel functions directly from the command line.