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 …
-
Show this thread
-
Replying to @RichFelker
I would consider a number (not all) of
@chandlerc1024's suggestions improvements to code quality. Move rarely-used paths out-of-line? Great!4 replies 0 retweets 6 likes -
Wait! Is LLVM much worse than GCC? I do benchmarks all the time, small and large, and if anything, LLVM often comes up on top.
2 replies 0 retweets 0 likes -
-
Replying to @johnregehr @lemire and
Lack of shrinkwrapping was one of my big complaints about both for a long long time, but GCC mostly fixed it.
1 reply 0 retweets 1 like -
Replying to @RichFelker @johnregehr and
LLVM does the complete opposite of shrinkwrapping. It hoists stack allocations all the way up thru inlining and block scopes...
1 reply 0 retweets 0 likes
...so that if there's any code path that uses a huge amount of stack space, all code paths do (blowing L1 and possibly blowing away stack).
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.