@phnt @Inginsub @Suiseiseki @dcc

> These people keep trying to outsmart compiler optimizations and 99% of the fail to do so.

Yeah. The dude that puts "register" in front of every variable declaration.

> At least from my point of view that is why compilers turned aggressive with optimizations, to silence these people

I think it's because they want the code to be faster and once you run out of shit to do, you can say "Well...it's undefined behavior if you do integer overflow so we can just assume that integer overflow never happens!" and they can continue fiddling with shit that wasn't broke until they "fixed" it. It's exciting to make code go 1% faster and it is not exciting to make the codebase cleaner and easier to read.

> The other reason might also be the increasing usage of C++ which literally is optimizer abuse.

I don't think it should be the same compiler. They can't make the same compiler produce binaries for two different architectures but they can make it accept source for 30 different languages. "Maybe some languages *shouldn't* be added to the gcc monolith" guy gets thrown out the window.