Re:Firefox nightly is now built with clang LTO on all platforms
by cptskippy on Wednesday September 12, 2018 @02:03PM
(#17971356)
> Considering the expected future advantages from using clang (cross-language inlining with Rust, consistency between platforms), it seemed a better deal to switch to clang than to try to address those issues.
No, they anticipated switching over to clang in the future so rather than spend "3 months" fighting GCC's linker then do it all over again switching to clang, they just switched.
Re:Firefox nightly is now built with clang LTO on all platforms
by topspin on Wednesday September 12, 2018 @03:03PM
(#17971982)
> So... they just gave up on gcc, and then per the remainder of the blog post spent "3 months" fighting linker behavior to get LTO working on clang?
Given that they're trying to align their C++ and Rust build tools -- the latter being based on LLVM -- the lack of interest in solving issues experienced with GCC is understandable. Also, given the complexity of the application and the platform diversity involved spending only "3 months" on such troubles is heroic performance.
Re:Firefox nightly is now built with clang LTO on all platforms
by sciurus on Wednesday September 12, 2018 @01:55PM
(#17971267)
The primary change wasn't away from GCC, it was away from MSVC.
https://groups.google.com/forum/m/#!topic/mozilla.dev.platfo...
Re:Firefox nightly is now built with clang LTO on all platforms
by mgbmtl on Wednesday September 12, 2018 @02:00PM
(#17971330)
The blog post does also say: "Considering the expected future advantages from using clang (cross-language inlining with Rust, consistency between platforms), it seemed a better deal to switch to clang than to try to address those issues."
Re:Firefox nightly is now built with clang LTO on all platforms
by dralley on Wednesday September 12, 2018 @02:00PM
(#17971320)
Clang LTO works between Rust and C++ - GCC can't do that.
Re:Firefox nightly is now built with clang LTO on all platforms
by steveklabnik on Wednesday September 12, 2018 @04:15PM
(#17972760)
will work; itβs in-progress, but not ready for the big times yet, as far as I know https://github.com/rust-lang/rust/issues/49879
So... they just gave up on gcc, and then per the remainder of the blog post spent "3 months" fighting linker behavior to get LTO working on clang? That seems like a surprising asymmetry, and makes me wonder if the reported performance gains weren't the real reason for the switch.