3 ms·
These changes seem like ones that the Chromium team would have already considered and opted out of. ultimately they need to support their product and the debug
by wyldfire 5y ago
These changes seem like ones that the Chromium team would have already considered and opted out of. ultimately they need to support their product and the debug features are for that purpose. Not picking max optimization helps avoid toolchain bugs. Using "-mllvm" flags from clang is asking for trouble.
That said, good for them. It's an achievement and if they can support their browser well, then it's the perfect reason for a fork - philosophical differences on how to design the software.
- LordFrick 5y agoHeller, dev here. Many mllvm flags can break stuff especially in chromium, but the LOOP optimizations I added have been extensively tested by me and robrich999, and only signal thinlto to more aggressively optimize, or for clang to do additional passes on loop functions that it is already optimizing for.