Thread: How to trash your code quality with awful hacks to make up for LLVM being so much worse than GCC.https://twitter.com/chandlerc1024/status/918034746587803648 …
-
-
Making silly transformations the compiler should be able to make can also be uglifying/obscuring:https://twitter.com/chandlerc1024/status/918037668436500480 …
-
"Let's go back to the 90s and start making random ugly source perturbations to help the optimizer" is not what LLVM should be bringing us.
End of conversation
New conversation -
-
-
When perf is important, factoring based on perf is appropriate. It'll also help both GCC and your own optimization efforts.
-
As a last resort, yes. Compiler tech should be eliminating that, though (LTO, etc.) not bringing it back.
-
I freely admit to doing the same fairly often, but it's not something I'm proud of or consider clean. It's "cos the compiler sucks".
-
It is the cleanest solution I know. There is a vast supply of compilers worse than LLVM that will need it, even if LLVM doesn't.
-
Unless one is fortunate to live in Cloudcuckooland where only ToT GCC or LLVM exists, that's the way it's gonna be.
-
GCC is really still the only compiler with near-universal target support and production-grade optimization.
-
That's not to say GCC is at all well-designed or clean, just that others have a long way to go achieving better with good design.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.