In April 2019 in https://bugs.webkit.org/show_bug.cgi?id=197131 <https://bugs.webkit.org/show_bug.cgi?id=197131> I increased WebKit’s minimum C++ language requirement from C++14 to C++17. In 2022 I’m planning to increase WebKit’s minimum C++ requirement from C++17 to C++20. Would April 2022 be a good time to do that?
I recently upgraded GCC requirement to 8.3.0 based on https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement <https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement> (https://trac.webkit.org/changeset/283348/webkit <https://trac.webkit.org/changeset/283348/webkit>) As a result, we can use some of C++20 features. I wonder if we can flip C++20 now. While some of C++20 features cannot be used since GCC 8.3.0 does not support, but some of features can be used, and it is super useful. One of the good features is initializer for bit-fields, which can avoid uninitialized bit-field bugs. class A { bool m_test : 1 : { false }; }; -Yusuke
On Dec 6, 2021, at 12:52 PM, Alex Christensen via webkit-dev <webkit-dev@lists.webkit.org> wrote:
In April 2019 in https://bugs.webkit.org/show_bug.cgi?id=197131 <https://bugs.webkit.org/show_bug.cgi?id=197131> I increased WebKit’s minimum C++ language requirement from C++14 to C++17. In 2022 I’m planning to increase WebKit’s minimum C++ requirement from C++17 to C++20. Would April 2022 be a good time to do that? _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
I’m also excited about using coroutines in WebKit. If there is already a GCC requirement for using a compiler that supports C++20, is there a reason not to switch from C++17 to C++20 later in 2021?
On Dec 6, 2021, at 2:36 PM, Yusuke Suzuki <ysuzuki@apple.com> wrote:
I recently upgraded GCC requirement to 8.3.0 based on https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement <https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement> (https://trac.webkit.org/changeset/283348/webkit <https://trac.webkit.org/changeset/283348/webkit>) As a result, we can use some of C++20 features. I wonder if we can flip C++20 now. While some of C++20 features cannot be used since GCC 8.3.0 does not support, but some of features can be used, and it is super useful. One of the good features is initializer for bit-fields, which can avoid uninitialized bit-field bugs.
class A { bool m_test : 1 : { false }; };
-Yusuke
On Dec 6, 2021, at 12:52 PM, Alex Christensen via webkit-dev <webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org>> wrote:
In April 2019 in https://bugs.webkit.org/show_bug.cgi?id=197131 <https://bugs.webkit.org/show_bug.cgi?id=197131> I increased WebKit’s minimum C++ language requirement from C++14 to C++17. In 2022 I’m planning to increase WebKit’s minimum C++ requirement from C++17 to C++20. Would April 2022 be a good time to do that? _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> https://lists.webkit.org/mailman/listinfo/webkit-dev
On Tue, Dec 7, 2021 at 8:07 AM Alex Christensen via webkit-dev < webkit-dev@lists.webkit.org> wrote:
I’m also excited about using coroutines in WebKit. If there is already a GCC requirement for using a compiler that supports C++20, is there a reason not to switch from C++17 to C++20 later in 2021?
Will you change WebKit's GCC version policy? If so, what will be the minimum supported versions of GCC, Clang and MSVC? According to the Clang C++ conformance page, it doesn't fully support Coroutines yet. Do you know which Clang version has started to support it partially? Which part of Coroutines is supported by the version of Clang? WebKitGTK/GCCRequirement – WebKit https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement Clang - C++ Programming Language Status https://clang.llvm.org/cxx_status.html C++ Standards Support in GCC - GNU Project https://gcc.gnu.org/projects/cxx-status.html Microsoft C/C++ language conformance | Microsoft Docs https://docs.microsoft.com/en-us/cpp/overview/visual-cpp-language-conformanc...
On 06/12/2021 22:36, Yusuke Suzuki via webkit-dev wrote:
I recently upgraded GCC requirement to 8.3.0 based on https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement <https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement> (https://trac.webkit.org/changeset/283348/webkit <https://trac.webkit.org/changeset/283348/webkit>) As a result, we can use some of C++20 features. I wonder if we can flip C++20 now. While some of C++20 features cannot be used since GCC 8.3.0 does not support, but some of features can be used, and it is super useful.
From the PoV of WebKitGTK I think it is Ok to enable now the building with C++-20 support and to start using the C++-20 features already supported by GCC 8.3.0
Check here: https://gcc.gnu.org/projects/cxx-status.html which C++-20 features are supported by GCC 8 Before using them I think it would be a good idea to double-check if those are also supported by the minimum version of Clang that we want to support. And maybe also to check if those are supported by MS Visual C++ ? I say maybe because I'm not sure if we support this compiler.
I, with great help from several of you, got https://bugs.webkit.org/show_bug.cgi?id=233963 <https://bugs.webkit.org/show_bug.cgi?id=233963> compiling on all platforms, but several of the JSC bots are still red. I’m under the impression that they either need a clean build or I’ve missed something. Could a JSC bot maintainer look into it?
On Dec 7, 2021, at 2:38 PM, Carlos Alberto Lopez Perez via webkit-dev <webkit-dev@lists.webkit.org> wrote:
On 06/12/2021 22:36, Yusuke Suzuki via webkit-dev wrote:
I recently upgraded GCC requirement to 8.3.0 based on https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement <https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement> (https://trac.webkit.org/changeset/283348/webkit <https://trac.webkit.org/changeset/283348/webkit>) As a result, we can use some of C++20 features. I wonder if we can flip C++20 now. While some of C++20 features cannot be used since GCC 8.3.0 does not support, but some of features can be used, and it is super useful.
From the PoV of WebKitGTK I think it is Ok to enable now the building with C++-20 support and to start using the C++-20 features already supported by GCC 8.3.0
Check here: https://gcc.gnu.org/projects/cxx-status.html which C++-20 features are supported by GCC 8
Before using them I think it would be a good idea to double-check if those are also supported by the minimum version of Clang that we want to support. And maybe also to check if those are supported by MS Visual C++ ? I say maybe because I'm not sure if we support this compiler. _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
We cannot use char8_t since it is not available in GCC 8.3.0 :) -Yusuke
On Jan 5, 2022, at 7:43 PM, Alex Christensen via webkit-dev <webkit-dev@lists.webkit.org> wrote:
I, with great help from several of you, got https://bugs.webkit.org/show_bug.cgi?id=233963 <https://bugs.webkit.org/show_bug.cgi?id=233963> compiling on all platforms, but several of the JSC bots are still red. I’m under the impression that they either need a clean build or I’ve missed something. Could a JSC bot maintainer look into it?
On Dec 7, 2021, at 2:38 PM, Carlos Alberto Lopez Perez via webkit-dev <webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org>> wrote:
On 06/12/2021 22:36, Yusuke Suzuki via webkit-dev wrote:
I recently upgraded GCC requirement to 8.3.0 based on https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement <https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement> <https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement <https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement>> (https://trac.webkit.org/changeset/283348/webkit <https://trac.webkit.org/changeset/283348/webkit> <https://trac.webkit.org/changeset/283348/webkit <https://trac.webkit.org/changeset/283348/webkit>>) As a result, we can use some of C++20 features. I wonder if we can flip C++20 now. While some of C++20 features cannot be used since GCC 8.3.0 does not support, but some of features can be used, and it is super useful.
From the PoV of WebKitGTK I think it is Ok to enable now the building with C++-20 support and to start using the C++-20 features already supported by GCC 8.3.0
Check here: https://gcc.gnu.org/projects/cxx-status.html <https://gcc.gnu.org/projects/cxx-status.html> which C++-20 features are supported by GCC 8
Before using them I think it would be a good idea to double-check if those are also supported by the minimum version of Clang that we want to support. And maybe also to check if those are supported by MS Visual C++ ? I say maybe because I'm not sure if we support this compiler. _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> https://lists.webkit.org/mailman/listinfo/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Related to the C++20 change, I’m working on moving the Visual Studio build to Visual Studio 2022. I’ve informed several involved parties directly, but now I’ve informed everyone. If anyone has a reason not to move to VS2022, please let me know.
On Jan 6, 2022, at 2:11 AM, Yusuke Suzuki <ysuzuki@apple.com> wrote:
We cannot use char8_t since it is not available in GCC 8.3.0 :)
-Yusuke
On Jan 5, 2022, at 7:43 PM, Alex Christensen via webkit-dev <webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org>> wrote:
I, with great help from several of you, got https://bugs.webkit.org/show_bug.cgi?id=233963 <https://bugs.webkit.org/show_bug.cgi?id=233963> compiling on all platforms, but several of the JSC bots are still red. I’m under the impression that they either need a clean build or I’ve missed something. Could a JSC bot maintainer look into it?
On Dec 7, 2021, at 2:38 PM, Carlos Alberto Lopez Perez via webkit-dev <webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org>> wrote:
On 06/12/2021 22:36, Yusuke Suzuki via webkit-dev wrote:
I recently upgraded GCC requirement to 8.3.0 based on https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement <https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement> <https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement <https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement>> (https://trac.webkit.org/changeset/283348/webkit <https://trac.webkit.org/changeset/283348/webkit> <https://trac.webkit.org/changeset/283348/webkit <https://trac.webkit.org/changeset/283348/webkit>>) As a result, we can use some of C++20 features. I wonder if we can flip C++20 now. While some of C++20 features cannot be used since GCC 8.3.0 does not support, but some of features can be used, and it is super useful.
From the PoV of WebKitGTK I think it is Ok to enable now the building with C++-20 support and to start using the C++-20 features already supported by GCC 8.3.0
Check here: https://gcc.gnu.org/projects/cxx-status.html <https://gcc.gnu.org/projects/cxx-status.html> which C++-20 features are supported by GCC 8
Before using them I think it would be a good idea to double-check if those are also supported by the minimum version of Clang that we want to support. And maybe also to check if those are supported by MS Visual C++ ? I say maybe because I'm not sure if we support this compiler. _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> https://lists.webkit.org/mailman/listinfo/webkit-dev <https://lists.webkit.org/mailman/listinfo/webkit-dev>
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> https://lists.webkit.org/mailman/listinfo/webkit-dev
It sounds nice! New CMake (3.21~) already supports VS 2022. -Yusuke
On Jan 21, 2022, at 10:36 AM, Alex Christensen <achristensen@apple.com> wrote:
Related to the C++20 change, I’m working on moving the Visual Studio build to Visual Studio 2022. I’ve informed several involved parties directly, but now I’ve informed everyone. If anyone has a reason not to move to VS2022, please let me know.
On Jan 6, 2022, at 2:11 AM, Yusuke Suzuki <ysuzuki@apple.com <mailto:ysuzuki@apple.com>> wrote:
We cannot use char8_t since it is not available in GCC 8.3.0 :)
-Yusuke
On Jan 5, 2022, at 7:43 PM, Alex Christensen via webkit-dev <webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org>> wrote:
I, with great help from several of you, got https://bugs.webkit.org/show_bug.cgi?id=233963 <https://bugs.webkit.org/show_bug.cgi?id=233963> compiling on all platforms, but several of the JSC bots are still red. I’m under the impression that they either need a clean build or I’ve missed something. Could a JSC bot maintainer look into it?
On Dec 7, 2021, at 2:38 PM, Carlos Alberto Lopez Perez via webkit-dev <webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org>> wrote:
On 06/12/2021 22:36, Yusuke Suzuki via webkit-dev wrote:
I recently upgraded GCC requirement to 8.3.0 based on https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement <https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement> <https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement <https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement>> (https://trac.webkit.org/changeset/283348/webkit <https://trac.webkit.org/changeset/283348/webkit> <https://trac.webkit.org/changeset/283348/webkit <https://trac.webkit.org/changeset/283348/webkit>>) As a result, we can use some of C++20 features. I wonder if we can flip C++20 now. While some of C++20 features cannot be used since GCC 8.3.0 does not support, but some of features can be used, and it is super useful.
From the PoV of WebKitGTK I think it is Ok to enable now the building with C++-20 support and to start using the C++-20 features already supported by GCC 8.3.0
Check here: https://gcc.gnu.org/projects/cxx-status.html <https://gcc.gnu.org/projects/cxx-status.html> which C++-20 features are supported by GCC 8
Before using them I think it would be a good idea to double-check if those are also supported by the minimum version of Clang that we want to support. And maybe also to check if those are supported by MS Visual C++ ? I say maybe because I'm not sure if we support this compiler. _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> https://lists.webkit.org/mailman/listinfo/webkit-dev <https://lists.webkit.org/mailman/listinfo/webkit-dev>
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> https://lists.webkit.org/mailman/listinfo/webkit-dev <https://lists.webkit.org/mailman/listinfo/webkit-dev>
While we’re updating things, is there any objection to updating the minimum version of CMake required? Right now it is 3.12, which was released in 2018. Does anyone have any limitations we should consider when picking a new minimum version?
On Jan 21, 2022, at 4:51 PM, Yusuke Suzuki <ysuzuki@apple.com> wrote:
It sounds nice! New CMake (3.21~) already supports VS 2022.
-Yusuke
On Jan 21, 2022, at 10:36 AM, Alex Christensen <achristensen@apple.com <mailto:achristensen@apple.com>> wrote:
Related to the C++20 change, I’m working on moving the Visual Studio build to Visual Studio 2022. I’ve informed several involved parties directly, but now I’ve informed everyone. If anyone has a reason not to move to VS2022, please let me know.
On Jan 6, 2022, at 2:11 AM, Yusuke Suzuki <ysuzuki@apple.com <mailto:ysuzuki@apple.com>> wrote:
We cannot use char8_t since it is not available in GCC 8.3.0 :)
-Yusuke
On Jan 5, 2022, at 7:43 PM, Alex Christensen via webkit-dev <webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org>> wrote:
I, with great help from several of you, got https://bugs.webkit.org/show_bug.cgi?id=233963 <https://bugs.webkit.org/show_bug.cgi?id=233963> compiling on all platforms, but several of the JSC bots are still red. I’m under the impression that they either need a clean build or I’ve missed something. Could a JSC bot maintainer look into it?
On Dec 7, 2021, at 2:38 PM, Carlos Alberto Lopez Perez via webkit-dev <webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org>> wrote:
On 06/12/2021 22:36, Yusuke Suzuki via webkit-dev wrote:
I recently upgraded GCC requirement to 8.3.0 based on https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement <https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement> <https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement <https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement>> (https://trac.webkit.org/changeset/283348/webkit <https://trac.webkit.org/changeset/283348/webkit> <https://trac.webkit.org/changeset/283348/webkit <https://trac.webkit.org/changeset/283348/webkit>>) As a result, we can use some of C++20 features. I wonder if we can flip C++20 now. While some of C++20 features cannot be used since GCC 8.3.0 does not support, but some of features can be used, and it is super useful.
From the PoV of WebKitGTK I think it is Ok to enable now the building with C++-20 support and to start using the C++-20 features already supported by GCC 8.3.0
Check here: https://gcc.gnu.org/projects/cxx-status.html <https://gcc.gnu.org/projects/cxx-status.html> which C++-20 features are supported by GCC 8
Before using them I think it would be a good idea to double-check if those are also supported by the minimum version of Clang that we want to support. And maybe also to check if those are supported by MS Visual C++ ? I say maybe because I'm not sure if we support this compiler. _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> https://lists.webkit.org/mailman/listinfo/webkit-dev <https://lists.webkit.org/mailman/listinfo/webkit-dev>
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org <mailto:webkit-dev@lists.webkit.org> https://lists.webkit.org/mailman/listinfo/webkit-dev <https://lists.webkit.org/mailman/listinfo/webkit-dev>
On 22/01/2022 01:51, Alex Christensen via webkit-dev wrote:
While we’re updating things, is there any objection to updating the minimum version of CMake required? Right now it is 3.12, which was released in 2018. Does anyone have any limitations we should consider when picking a new minimum version?
Yes. CMake is one of the core dependencies for GTK and WPE ports, so the policy of dependencies applies [1] In practical terms that means that we should support the version of CMake shipped by Debian 10, which is CMake 3.13 until at least 2022-08-14. However, If the purpose of raising the version is to take advantage of the new Visual Studio generator then I don't think raising the minimum version is needed. As far as I know you can take advantage of newer CMake features (like support for a newer generator) without needing to raise the minimum version required. So if you have a newer version of CMake you can simply pass the flag -G"Visual Studio 17 2022" (or similar). Raising the minimum version required of CMake is not needed to use a newer CMake generator, using it can be made optional for those that want (and can) use it. [1] https://trac.webkit.org/wiki/WebKitGTK/DependenciesPolicy
Ok. We won’t raise the minimum CMake version for all of WebKit right now then, just on Windows when we start requiring VS2022.
On Jan 22, 2022, at 1:44 PM, Carlos Alberto Lopez Perez via webkit-dev <webkit-dev@lists.webkit.org> wrote:
On 22/01/2022 01:51, Alex Christensen via webkit-dev wrote:
While we’re updating things, is there any objection to updating the minimum version of CMake required? Right now it is 3.12, which was released in 2018. Does anyone have any limitations we should consider when picking a new minimum version?
Yes.
CMake is one of the core dependencies for GTK and WPE ports, so the policy of dependencies applies [1]
In practical terms that means that we should support the version of CMake shipped by Debian 10, which is CMake 3.13 until at least 2022-08-14.
However, If the purpose of raising the version is to take advantage of the new Visual Studio generator then I don't think raising the minimum version is needed.
As far as I know you can take advantage of newer CMake features (like support for a newer generator) without needing to raise the minimum version required.
So if you have a newer version of CMake you can simply pass the flag -G"Visual Studio 17 2022" (or similar). Raising the minimum version required of CMake is not needed to use a newer CMake generator, using it can be made optional for those that want (and can) use it.
[1] https://trac.webkit.org/wiki/WebKitGTK/DependenciesPolicy _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Apple and Sony are finishing updating our build infrastructure to Visual Studio 2022, and we are considering requiring it to build WebKit starting next week. If anyone has a reason to delay further, please let me know on this list or directly.
On Jan 24, 2022, at 1:43 PM, Alex Christensen via webkit-dev <webkit-dev@lists.webkit.org> wrote:
Ok. We won’t raise the minimum CMake version for all of WebKit right now then, just on Windows when we start requiring VS2022.
On Jan 22, 2022, at 1:44 PM, Carlos Alberto Lopez Perez via webkit-dev <webkit-dev@lists.webkit.org> wrote:
On 22/01/2022 01:51, Alex Christensen via webkit-dev wrote:
While we’re updating things, is there any objection to updating the minimum version of CMake required? Right now it is 3.12, which was released in 2018. Does anyone have any limitations we should consider when picking a new minimum version?
Yes.
CMake is one of the core dependencies for GTK and WPE ports, so the policy of dependencies applies [1]
In practical terms that means that we should support the version of CMake shipped by Debian 10, which is CMake 3.13 until at least 2022-08-14.
However, If the purpose of raising the version is to take advantage of the new Visual Studio generator then I don't think raising the minimum version is needed.
As far as I know you can take advantage of newer CMake features (like support for a newer generator) without needing to raise the minimum version required.
So if you have a newer version of CMake you can simply pass the flag -G"Visual Studio 17 2022" (or similar). Raising the minimum version required of CMake is not needed to use a newer CMake generator, using it can be made optional for those that want (and can) use it.
[1] https://trac.webkit.org/wiki/WebKitGTK/DependenciesPolicy _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
That’s awesome! Thank you for your work! -Yusuke
On Mar 9, 2022, at 4:29 PM, Alex Christensen via webkit-dev <webkit-dev@lists.webkit.org> wrote:
Apple and Sony are finishing updating our build infrastructure to Visual Studio 2022, and we are considering requiring it to build WebKit starting next week. If anyone has a reason to delay further, please let me know on this list or directly.
On Jan 24, 2022, at 1:43 PM, Alex Christensen via webkit-dev <webkit-dev@lists.webkit.org> wrote:
Ok. We won’t raise the minimum CMake version for all of WebKit right now then, just on Windows when we start requiring VS2022.
On Jan 22, 2022, at 1:44 PM, Carlos Alberto Lopez Perez via webkit-dev <webkit-dev@lists.webkit.org> wrote:
On 22/01/2022 01:51, Alex Christensen via webkit-dev wrote:
While we’re updating things, is there any objection to updating the minimum version of CMake required? Right now it is 3.12, which was released in 2018. Does anyone have any limitations we should consider when picking a new minimum version?
Yes.
CMake is one of the core dependencies for GTK and WPE ports, so the policy of dependencies applies [1]
In practical terms that means that we should support the version of CMake shipped by Debian 10, which is CMake 3.13 until at least 2022-08-14.
However, If the purpose of raising the version is to take advantage of the new Visual Studio generator then I don't think raising the minimum version is needed.
As far as I know you can take advantage of newer CMake features (like support for a newer generator) without needing to raise the minimum version required.
So if you have a newer version of CMake you can simply pass the flag -G"Visual Studio 17 2022" (or similar). Raising the minimum version required of CMake is not needed to use a newer CMake generator, using it can be made optional for those that want (and can) use it.
[1] https://trac.webkit.org/wiki/WebKitGTK/DependenciesPolicy _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
On 06/12/2021 20:52, Alex Christensen via webkit-dev wrote:
In April 2019 in https://bugs.webkit.org/show_bug.cgi?id=197131 <https://bugs.webkit.org/show_bug.cgi?id=197131> I increased WebKit’s minimum C++ language requirement from C++14 to C++17. In 2022 I’m planning to increase WebKit’s minimum C++ requirement from C++17 to C++20. Would April 2022 be a good time to do that?
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
According to the WebKitGTK Dependencies policy [1], we have to support GCC-8 until August 2022. But we would like, if possible, to support it until October 2022 which is when we will branch for doing the 2.38.x releases. That way we can do one more official release supporting GCC-8. Then, after October 2022 we can raise the minimum GCC requirement to GCC-9. On April 2023 we can raise the minimum GCC requirement to GCC-10 and so on. So this will be the timeline of minimum versions required that would fit our policy: - Now until October 2022 -> GCC-8 - October 2022 - April 2023 -> GCC-9 - April 2023 - 2024 -> GCC-10 Depending on the minimum GCC version required some C++-20 features can be used. You can check those on this "C++20 Language Features" table [2] Some examples that were brought here: - initializer for bit-fields -> GCC-8 (so that can be used already now) - coroutines -> GCC-10 (will have to wait until April 2023) Regards! -------- [1] https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement [2] https://gcc.gnu.org/projects/cxx-status.html
participants (4)
-
Alex Christensen
-
Carlos Alberto Lopez Perez
-
Fujii Hironori
-
Yusuke Suzuki