On Fri, Dec 07, 2018 at 10:57:41AM -0500, Gabriele Svelto wrote:
On 06/12/18 15:39, Kris Maglione wrote:
As it stands, we need to remain compatible with at least GCC and Clang,
because some of our static analysis code still depends on GCC plugins.

Some Linux distros will keep building Firefox with GCC so there's going
to be at least some external users of that particular combination. MSVC
is a different story since nobody else would be using it.

I'm not sure how long that's going to be viable, at least for branded builds. GCC's optimizers already generate significantly slower code than clang's, and the disadvantage is going to get much worse when we have cross-language inlining in our clang builds, which GCC will never be able to support.

If they want to continue shipping GCC builds with their own branding, I suppose that's fine, but I don't think that would be a good reason for us to continue investing effort into supporting it.
dev-platform mailing list

Reply via email to