Of course not. I don't care for gcc's broken optimizer to remove dead code without any warning.
gcc has too many bugs for my taste, sorry. And I don't want to wait 20m on gcc compilation, when tcc can do it in 1m.
gcc has too many bugs for my taste, sorry. And I don't want to wait 20m on gcc compilation, when tcc can do it in 1m.
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.
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.