&gt; What I find lacking in web pages is a motivationFrom those pages:&quot;The purpose of Kefir project is producing an independent C17&#x2F;C23 compiler with
well-rounded architecture and well-defined scope that is feasible for implementation by a single developer.&quot;He wants a third compiler to vet code portability. He wants it simple enough to build and maintain himself.

I remember when we still had tcc in Neovim CI. I think it got removed eventually for being too much of a burden to maintain.How are slimcc&#x2F;kefir different&#x2F;easier to drop in?

I have found portability bugs in many projects with slimcc just because it exposed different preprocessor defines, some gate critical __attribute__ behind __GNUC__ check, some have buggy fallback to __builtin functions or VLA that nobody noticed in years, these could have been avoided with just an automatic build job in the CI with kefir or slimcc, (tcc is awesome but less suited for being a drop-in).It is also important to have more independent implementations of the C standard, not only to sort out dark corners in the specification (current WG14 have been doing great), but to prevent it turning into GCC-Clang power struggle.

Those sections don&#x27;t really provide details on the author&#x27;s motivations to be honest

I agree on it being fantastic.For your other questions I found these in the linked text<pre><code> - https:&#x2F;&#x2F;sr.ht&#x2F;~jprotopopov&#x2F;kefir&#x2F;#goals-and-priorities
 - https:&#x2F;&#x2F;sr.ht&#x2F;~jprotopopov&#x2F;kefir&#x2F;#history-and-future-plans</code></pre>

I think it is fantastic to have more compiler implementations. It was probably also a fun project to code. What I find lacking in web pages is a motivation. What makes it different from popular compilers? Where is this project heading? What would be potential benefits&#x2F;use-cases for using this compiler vs others, lessons learned, etc.?

You could use cproc&#x2F;qbe, tinycc, scc, etc. The more real-like C compiler implementations the better.

This is something that intrigues me:
&quot;Is able to output internal representations (tokens, abstract syntax tree, intermediate representation) in machine-readable JSON form.&quot;I&#x27;m not sure what I can do with that information but I wish I had an excuse to use it

c-testsuite itself was curated from simple-cc and tinycc&#x27;s test files, the latter originated from picoc.

c-testsuite is not made by the author of Kefir.

It&#x27;s amazing how much one motivated person can achieve. Also, how competent the result seems to be. The test suite alone is pretty impressive.

Very impressive for a single dev project.Nice to see someone started the work from zero instead of piggybacking LLVM.

Congrats for the new optimizing pipeline, and thanks for the acknowledgment! It&#x27;s nice to have company in the non-__GNUC__ camp.

Kefir C17/C23 Compiler