[Webkit-unassigned] [Bug 174155] Upgrade GCC baseline

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=174155

--- Comment #4 from Carlos Alberto Lopez Perez <clopez at igalia.com> ---
(In reply to Yusuke Suzuki from comment #3)
> (In reply to Michael Catanzaro from comment #2)
> > GTK and WPE are ready for GCC 5, except for a couple nonessential bots that
> > are not run by Igalia. We would prefer to defer requiring GCC 6 until next
> > summer.
> 
> Anyway, the large part of C++17 is shipped in GCC 7. So I think if we would
> like to use C++17, we need to upgrade GCC to 7 at least.
> So, personally, GCC 5 for now seems fine to me.
> It would be nice if we can upgrade our GCC to 7 next summer...
> 

According to https://trac.webkit.org/wiki/WebKitGTK/DependenciesPolicy

* Its fine to require now at least GCC 5.3 (that is what Ubuntu 16.04 ships)

* On May of 2018 (when Ubuntu 18.04 will be released -- next LTS) it will be fine to require at least GCC 6.3 (that is what Debian 9 ships currently).

* It won't be fine to require GCC >= 7 until at least 2019-2020 (when Debian 10 will be released)


I understand the desire to use new compiler features, but at the same time I understand that requiring a too much new version of the compiler will cause trouble for many users. This is specially true for embedded users where the version of the compiler/toolchain is not something you can upgrade easier.

I think our current policy is a good compromise between using new compiler features and allowing WebKit to be built with a reasonably old toolchain.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170705/bb013989/attachment.html>