Re: Stable update to newer GCC versions soon?
Hamish McIntyre-Bhatty via Cygwin-apps <[email protected]> Sat, 21 Mar 2026 17:09:24 +0000
| Newsgroups | gmane.os.cygwin.applications |
|---|---|
| Message-ID | <[email protected]> |
On 20/03/2026 20:05, Brian Inglis via Cygwin-apps wrote: > On 2026-03-20 10:20, Hamish McIntyre-Bhatty via Cygwin-apps wrote: >> On 19/03/2026 20:16, Brian Inglis via Cygwin-apps wrote: >>> On 2026-03-19 09:10, Hamish McIntyre-Bhatty via Cygwin-apps wrote: >>>> I see that there are test packages for newer versions of GCC, but >>>> the stable packages remains on the older GCC 13. I've encountered >>>> internal compiler errors when compiling unit tests for python- >>>> pybind11, and I was wondering why the test versions haven't been >>>> marked stable yet, as they might fix the issue. >>>> >>>> If the answer is that more testing needs to be done then I may >>>> volunteer myself for that as it would probably benefit me to have a >>>> newer stable compiler. Also, can I report the internal compiler >>>> errors upstream or can I not due to downstream Cygwin patches? >>> >>> GCC packages are normally considered stable when they reach V.4... >>> which for V14 might have been expected to be last ~August but now >>> may not be until ~May or ~August? >> >> Oh, okay, I wasn't aware of that, and a quick search suggests that >> they should be stable from the V.1 release, which is in keeping with >> when many common Linux distros update? Am I missing something, or is >> this just when the Cygwin packages are considered stable? > > GCC regression testing is not really complete until V.4... is > released, so I think as we support only one current stable version, > that is the level required to trust as default for building the base > and packages. > It also gives us quite some time to test against the base and packages. Ah okay, makes sense. Should I report internal compiler errors upstream or to Cygwin then? I guess I should probably just go check if there are a lot of patches for Cygwin support in GCC, or if it's just all upstreamed? > >>> https://gcc.gnu.org/gcc-13/ >>> >>> Release History >>> >>> GCC 13.4 >>> June 5, 2025 (changes, documentation) >>> GCC 13.3 >>> May 21, 2024 (changes, documentation) >>> GCC 13.2 >>> July 27, 2023 (changes, documentation) >>> GCC 13.1 >>> April 26, 2023 (changes, documentation) >>> >>> https://gcc.gnu.org/gcc-14/ >>> >>> Release History >>> >>> GCC 14.3 >>> May 23, 2025 (changes, documentation) >>> GCC 14.2 >>> Aug 1, 2024 (changes, documentation) >>> GCC 14.1 >>> May 7, 2024 (changes, documentation) >>> >>> https://gcc.gnu.org/gcc-15/ >>> >>> Release History >>> >>> GCC 15.2 >>> August 8, 2025 (changes, documentation) >>> GCC 15.1 >>> April 25, 2025 (changes, documentation) >>> >>> https://gcc.gnu.org/gcc-16/ >>> >>> https://gcc.gnu.org/gcc-16/criteria.html >>> >>> Source Package: gcc >>> >>> summary: GNU Compiler Collection >>> ... >>> Version Arch... Date ...Status Files >>> ... >>> 11.4.0-1 src... 2023-06-05 ...stable .../gcc-11.4.0-1-src >>> 11.5.0-1 src... 2024-07-21 ...stable .../gcc-11.5.0-1-src >>> 12.4.0-3 src... 2024-07-29 ...stable .../gcc-12.4.0-3-src >>> 12.5.0-1 src... 2025-07-13 ...stable .../gcc-12.5.0-1-src >>> 13.4.0-1 src... 2025-06-15 ...stable .../gcc-13.4.0-1-src >>> 14.3.1+20260206-0.1 src... 2026-02-11 ... test .../ >>> gcc-14.3.1+20260206-0.1-src >>> 15.2.1+20260207-0.1 src... 2026-02-11 ... test .../ >>> gcc-15.2.1+20260207-0.1-src >>> 16.0.0+20260208-0.1 src... 2026-02-15 ... test .../ >>> gcc-16.0.0+20260208-0.1-src >>> >> > >