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/use-cases for using this compiler vs others, lessons learned, etc.?
> What I find lacking in web pages is a motivation
From those pages:
"The purpose of Kefir project is producing an independent C17/C23 compiler with
well-rounded architecture and well-defined scope that is feasible for implementation by a single developer."
He wants a third compiler to vet code portability. He wants it simple enough to build and maintain himself.
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.
Can't speak for kefir; slimcc has been `make unittest`ing Neovim v0.10.4 with no source modification in a Debian VM (so it's pretty portable, thanks!)
On tcc, the most common dealbreaker is no thread local support, having independent assembler/linker is a wonderful feat but not being feature parity with binutils could lead to build failure, contributors generally less willing to support the correct behavior for ABI, C standards and GCC extensions.
I hope these don't sound like a diss, if I had been better at reading its coding style I would definitely try to contribute to mob branch.
I think they provide enough information to take a reasonable guess. It seems likely to me that the author is the type of programmer who prefers to understand what their code is doing, with as little magic involved as possible. Using other people's compilers is very magical, all kinds of transformations are being applied to the code you wrote and you are relying entirely on abstractions without really knowing how your code translates to controlling the hardware. Some people prefer to know exactly that.
This is something that intrigues me:
"Is able to output internal representations (tokens, abstract syntax tree, intermediate representation) in machine-readable JSON form."
I'm not sure what I can do with that information but I wish I had an excuse to use it
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/use-cases for using this compiler vs others, lessons learned, etc.?
> What I find lacking in web pages is a motivation
From those pages:
"The purpose of Kefir project is producing an independent C17/C23 compiler with well-rounded architecture and well-defined scope that is feasible for implementation by a single developer."
He wants a third compiler to vet code portability. He wants it simple enough to build and maintain himself.
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.
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/kefir different/easier to drop in?
Can't speak for kefir; slimcc has been `make unittest`ing Neovim v0.10.4 with no source modification in a Debian VM (so it's pretty portable, thanks!)
On tcc, the most common dealbreaker is no thread local support, having independent assembler/linker is a wonderful feat but not being feature parity with binutils could lead to build failure, contributors generally less willing to support the correct behavior for ABI, C standards and GCC extensions.
I hope these don't sound like a diss, if I had been better at reading its coding style I would definitely try to contribute to mob branch.
Thanks for the notes. Different as/link is definitely a way for incompatibilities to creep in.
I agree on it being fantastic.
For your other questions I found these in the linked text
Those sections don't really provide details on the author's motivations to be honest
I think they provide enough information to take a reasonable guess. It seems likely to me that the author is the type of programmer who prefers to understand what their code is doing, with as little magic involved as possible. Using other people's compilers is very magical, all kinds of transformations are being applied to the code you wrote and you are relying entirely on abstractions without really knowing how your code translates to controlling the hardware. Some people prefer to know exactly that.
This is something that intrigues me: "Is able to output internal representations (tokens, abstract syntax tree, intermediate representation) in machine-readable JSON form."
I'm not sure what I can do with that information but I wish I had an excuse to use it
You could use cproc/qbe, tinycc, scc, etc. The more real-like C compiler implementations the better.
It's amazing how much one motivated person can achieve. Also, how competent the result seems to be. The test suite alone is pretty impressive.
c-testsuite is not made by the author of Kefir.
c-testsuite itself was curated from simple-cc and tinycc's test files, the latter originated from picoc.
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's nice to have company in the non-__GNUC__ camp.
Can it compile Doom?