If you're just declaring gcc broken and removing its functionality, then why compare yourself to it? For any of the metrics you're using to hold water, you want the project to actually be comparable to gcc in terms of features, otherwise you could just remove half of their features and declare yourself as more efficient because half of gcc would compile faster than gcc.

And why are you talking about the optimizer? What I'm curious about is whether this compiler will successfully compile any project that can be compiled with gcc. Will it?

In addition to build time comparisons not meaning anything if the projects aren't equivalent, I also just don't get why it's so important. Most people don't spend their days recompiling gcc, they just want it to compile their projects quickly and accurately.

It compiles the kernel and my big projects, but I haven't released it yet.

Feature wise I don't do bitint, decimal and FloatX. No auto-vectorization, but better than most simd/neon projects, which don't use __attribute__((vector_size(N))). Manual vectorization.

no sanitizers nor flto.

rcc is for the people who want to compile their projects sanily, and fast. And who want to find unicode attacks. And for those who run into tcc bugs, there are many still. gcc and clang are insanily slow.

C compilers are already so fast... Now a fast C++ or rust compiler would be useful.