It's a fun comparison, but with the notable difference that that one can compile the Linux kernel and generate code for multiple different architectures, while this one can only compile a small proportion of valid C. It's a great project, but it's not so much a C compiler, as a compiler for a subset of C that allows all programs this compiler can compile to also be compiled by an actual C compiler, but not vice versa.
replyBut can it compile "Hello, World" example from its own README.md?
replyNoticed the part where all it requires is to actually have the headers in the right location?
reply"The location of Standard C headers do not need to be supplied to a conformant compiler."
replyFrom https://news.ycombinator.com/item?id=46920922 discussion.
And it doesn't for the compiler in question either. As long as the headers exist in the places it looks for them. No compiler magically knows where the headers are if you haven't placed them in the right location
replystddef.h (et al) should be shipped by the compiler itself, and so it should know where it is. But they rely on gcc for it, hence it doesn't always know where to look. Seems totally fine for a prototype.
replyEspecially given they're not shipping anything. The GCC binaries can't find misplaced or not installed headers either.
replyWould you accept the same quality of implementation from a human team?
replyA compiler that can't magically know how to find headers that don't exist in the expected directory?
replyYes, that is the case for pretty much every compiler. I suppose you could build the headers into the binary, but nobody does that.
It's fascinating how few people read past the issue title
replydeleted
reply