except it's... all wrong: this dependency-free compiler has a hard dependency on gcc (even as it's claiming it's a drop-in replacement), it has so many hardcoded paths, etc.
If more people are able to step back and think about the potential growth for the next 5-10 years, then I think the discussion would be very different.
I am grateful to be able to witness all these amazing progress play out, but am also concerned about the wide ranging implications.
There is a massive difference between a result like this when it's a research project and when it's being pushed by billion dollar companies as the solution to all of humanities problems.
In business, as a product, results are all that matter.
As a research and development efforts it's exciting and interesting as a milestone on the path to something revolutionary.
But I don't think it's ready to deliver value. Building a compiler that almost works is of no business value.
Noone can correctly quantify what these models can and can't do. That leads to the people in charge completely overselling them (automating all white collar jobs, doing all software engineering, etc) and the people threatened by those statements firing back when these models inevitably fail at doing what was promised.
They are very capable but it's very hard to explain to what degree. It is even harder to quantify what they will be able to do in the future and what inherent limits exist. Again leading to the people benefiting from it to claim that there are no limits.
Truth is that we just don't know. And there are too few good folks out there that are actually reasonable about it because the ones that know are working on the tech and benefit from more hype. Karpathy is one of the few that left the rocket and gives a still optimistic but reasonable perspective.
How does a statistical model become "perfect" instead of merely approaching it? What do you even mean by "perfect"?
We already have determinism in all machines without this wasteful layer of slop and indirection, and we're all sick and tired of the armchair philosophy.
It's very clear where LLMs will be used and it's not as a compiler. All disagreements with that are either made in bad faith or deeply ignorant.
Ah, two megapixel-PNG screenshots of console text (one hidpi too!), and of some IDE showing also text (plus a lot of empty space)... Great great job, everyone.
It really can replace human engineers. Mistakes and all. I've definitely written an "example" that I didn't actually test only to find out it doesn't work
I wonder if it feels the same embarrassment and shame I do too
Seems like a nothingburger? Mostly a spammy GitHub thread of people not reading the rest of the responses.
> Works if you supply the correct include path(s)
> Can confirm, works fine:
> You could arguably fault ccc's driver for not specifying the include path to find the native C library on this system.
> (I followed the instructions in the BUILDING_LINUX.txt file in the repo and got the kernel built for RISC-V. You can find the build I made here if someone is just interested in the binaries)
>> Works if you supply the correct include path(s)
The location of Standard C headers do not need to be supplied to a conformant compiler.
>> You could arguably fault ccc's driver for not specifying the include path to find the native C library on this system.
This is not a good implementation decision for a compiler which is not the C compiler distributed with the OS. Even though Standard C headers have well-defined names and public contracts, how they are defined is very much compiler specific.
They had GCC to use as an oracle/source of truth. Humans intervened multiple times. Clearly writing C compilers is a huge part of its training data—the literal definition of training on test data.
Wake me up when a model trained only on data through the year 1950 can write a C compiler.
The anti-AI crowd proves that they do need replacing as programmers since it was user error. Opus 4.6/ChatGPT 5.3 xhigh is superior to the vast majority of programmers. Talk about grasping for straws.
This will do the rounds on the front page of reddit with no mention of the users c library paths having issues as the root cause despite the clear error message stating that.
nextaccountic|24 days ago
https://github.com/anthropics/claudes-c-compiler/issues/1#is...
rf15|23 days ago
nomel|24 days ago
parker-3461|24 days ago
I am grateful to be able to witness all these amazing progress play out, but am also concerned about the wide ranging implications.
gtowey|24 days ago
In business, as a product, results are all that matter.
As a research and development efforts it's exciting and interesting as a milestone on the path to something revolutionary.
But I don't think it's ready to deliver value. Building a compiler that almost works is of no business value.
politelemon|24 days ago
jascha_eng|24 days ago
They are very capable but it's very hard to explain to what degree. It is even harder to quantify what they will be able to do in the future and what inherent limits exist. Again leading to the people benefiting from it to claim that there are no limits.
Truth is that we just don't know. And there are too few good folks out there that are actually reasonable about it because the ones that know are working on the tech and benefit from more hype. Karpathy is one of the few that left the rocket and gives a still optimistic but reasonable perspective.
DustinEchoes|24 days ago
sublinear|24 days ago
We already have determinism in all machines without this wasteful layer of slop and indirection, and we're all sick and tired of the armchair philosophy.
It's very clear where LLMs will be used and it's not as a compiler. All disagreements with that are either made in bad faith or deeply ignorant.
Insanity|24 days ago
largbae|24 days ago
rsynnott|24 days ago
netsharc|24 days ago
chvid|24 days ago
Incipient|24 days ago
d_silin|24 days ago
culi|24 days ago
I wonder if it feels the same embarrassment and shame I do too
helloplanets|24 days ago
politelemon|24 days ago
embedding-shape|24 days ago
> Works if you supply the correct include path(s)
> Can confirm, works fine:
> You could arguably fault ccc's driver for not specifying the include path to find the native C library on this system.
> (I followed the instructions in the BUILDING_LINUX.txt file in the repo and got the kernel built for RISC-V. You can find the build I made here if someone is just interested in the binaries)
AdieuToLogic|24 days ago
The location of Standard C headers do not need to be supplied to a conformant compiler.
>> You could arguably fault ccc's driver for not specifying the include path to find the native C library on this system.
This is not a good implementation decision for a compiler which is not the C compiler distributed with the OS. Even though Standard C headers have well-defined names and public contracts, how they are defined is very much compiler specific.
So this defect is a "somethingburger."
airstrike|24 days ago
Wake me up when a model trained only on data through the year 1950 can write a C compiler.
Der_Einzige|24 days ago
culi|24 days ago
AnotherGoodName|24 days ago