claudes-c-compiler

You missed this from last year https://github.com/anthropics/claudes-c-compiler Also I dunno why you should be impressed by this - gcc isn't anything near eg navier stokes

How is that going for Claude's C compiler [0], or Cursor's web browser? [1] [0] https://github.com/anthropics/claudes-c-compiler [1] https://github.com/wilsonzlin/fastrender

> As of writing, Claude Code CLI only has around 9100 open Github issues, with small unresolved issues like it completely freezing for the last 6+ months or a screen flickering issue open for more than a year. But surely those fully autonomous coding loops will solve all those 9,100+ open issues on GitHub? Why haven't they? What happened to Claude's C Compiler [0], or that browser "built from scratch" by Cursor? [1] Why aren't the agents maintaining it if they are supposed to be cheaper than humans? > But why do they have us by the balls? Dario and Boris have us convinced that “coding is solved” with their loops. But microwaves didn’t solve cooking. They have you by the balls if you allow them to, if you continue to listen to their bullshit. Both of them are essentially salesmen at this point. They don't care if they are wrong and will se

Ah, that reminded me to check up on these "AI wonder projects". Cursor's Web Browser? Last update 5 months ago: https://github.com/wilsonzlin/fastrender The Claude C compiler? 4 months since any changes: https://github.com/anthropics/claudes-c-compiler Zero moderation too, nice. https://github.com/anthropics/claudes-c-compiler/issues/264#... CloudFlare's slop NextJS project is still going though. https://github.com/cloudflare/vinext

When was the last time Claude's C Compiler was updated? 4 months ago? [0] It is written in Rust™, surely it is better than the rest of them. [0] https://github.com/anthropics/claudes-c-compiler

Part of the problem is that of human alienation. By excluding humans in the construction process, it has taken away any skin-in-the-game for humans. So, there could be a point where some bugs become unresolvable because LLMs dont have an adequate causal model and fixes by trial-and-error wont work in cases where root-causes are not properly addressed - and the project gets abandoned as a result. Witness the C compiler in rust [1], what happened to that after the initial press releases ? [1] https://github.com/anthropics/claudes-c-compiler

Why are you quoting from their marketing blog as if it's a reliable source? https://github.com/anthropics/claudes-c-compiler/issues/1 > Apparently compiling hello world exactly as the README says to is an unfair expectation of the software.

Strange subthread. I don't see Claude Opus 4.6 changing the tide for PyPy. There is no need to understate AI capabilities for this. "Anthropic released vibe coded C compiler that doesn't work" sounds like https://github.com/anthropics/claudes-c-compiler/issues/1 passed through a game of telephone. The compiler has some wrong defaults that prevent it from straightforwardly building a "Hello, world!" like GCC and Clang. The compiler works: > The 100,000-line compiler can build a bootable Linux 6.9 on x86, ARM, and RISC-V. It can also compile QEMU, FFmpeg, SQlite, postgres, redis, and has a 99% pass rate on most compiler test suites including the GCC torture test suite. It also passes the developer's ultimate litmus test: it can compile and run Doom. https://www.anthropic.com/engineering/building-c-compiler

> At this point though, after Claude C Compiler, Perfect example. You mean the C compiler that literally failed to compile a hello world [0] (which was given in it's readme)? > What do you consider simple issues? Hallucinating APIs for well documented libraries/interfaces, ignoring explicit instructions for how to do things, and making very simple logic errors in 30-100 line scripts. As an example, I asked Claude code to help me with a Roblox game last weekend, and specifically asked it to "create a shop GUI for <X> which scales with the UI, and opens when you press E next to the character". It proceeded to create a GUI with absolute sizings, get stuck on an API hallucination for handling input, and also, when I got it unstuck, it didn't actually work. [0] https://github.com/anthropics/claudes-c-compiler/issues/1

>I found this was the least impressive bit about it https://github.com/anthropics/claudes-c-compiler/issues/1 So, I just skimmed the discussion thread, but I am not seeing how this shows that CCC is not impressive. Is the point you're making that the person who opened the issue is not impressive?

I found this was the least impressive bit about it https://github.com/anthropics/claudes-c-compiler/issues/1

Deliver what exactly? False hope and lies? https://github.com/anthropics/claudes-c-compiler/issues/228

They definitely have access to the source code, look at the binutils entry [1], Claude was debugging compilation of "preprocessor #define inside #ifdef"'s in binutils's code. [1] https://github.com/anthropics/claudes-c-compiler/blob/6f1b99...

Didn't see people mention this in the initial discussion, but despite not having access to internet, the agents actually had access to the source code of GNU binutils (has assembler, linker and readelf), and many C compilers (SDCC, PCC, chibicc, cproc, etc) in their working directory [1]. These are supposed to test compilation, but there's no way to prove that Claude didn't get crucial info from these projects. I also found the compiler to have uncanny resemblance with chibicc. With 30-ish edge cases[2] yielding the same behavior, it's hard to believe there's no influence of chibicc in its algorithms. [1] https://github.com/anthropics/claudes-c-compiler/blob/6f1b99... [2] https://github.com/anthropics/claudes-c-compiler/issues/232