@Suiseiseki @Inginsub @dcc @phnt

> Bloat.

You wanna compare line counts between gcc and tcc?

> It's extremely fast, it just does a lot of checks and optimizations - you can disable the optimization and it's faster.

You've never used a fast compiler. Give it -O0 and then try kencc. gcc -O0 is *slower* than tcc and kencc.

> but not a problem,

It indicates that the project's technical direction has slipped.

> as a previous version that implemented the permitted subset of C++ in all C.

Let me tack this onto the list of things that make gcc the worst compiler that I have to use.

> Yes, it was always free software and was and is never proprietary software.

A legal distinction that does not matter. kencc has always had a relatively permissive license and the version included with Inferno was GPL for years before the Plan 9 version was GPL'd.

> Internally it is quite well structured, the number of features is just pushed to the limit.

$ man gcc | wc
25590 144392 1237729

Bloat.

$ ssh rex man gcc | wc
28759 158314 1369922

And it's only getting bigger.

> It is a second-class architecture,

I am vomit.

> Then don't write the software wrong

I never have. gcc has decided to fuck with me in new and exciting ways. The gcc authors can -fomit-frame-pointer my goddamn dick.

> or disable those optimizations flags then.

If I've got to write 2kB of options to make the compiler act like a real compiler for a real OS, then the compiler is a failure. If the compiler *accepts* 2kB of options, the compiler is a failure.

> Not really?

Yes, absolutely terrible. It is actually easier to use qemu-binfmt and a cross-arch chroot than to attempt to cross-compile a system using gcc.

> Breaking any possible proprietary software between minor versions is a good thing.

I have to maintain the distcc cluster's gcc versions in lockstep because the authors cannot keep their shit together.

> I haven't seen that, but it doesn't seem to be an issue with GCC.

Because you never attempt to statically link a program so that the GNU/Clusterfuck is able to keep up.

I attempted running "tig" in ~/src/gcc when I wrote "gcc authors" up near the beginning of this post and it still has not presented me with a screen full of commits so I'm not going back and changing it. gcc is bloated and barely functions and its codebase is like a shantytown on pontoons in the middle of the ocean.