diff --git a/website/content/en/status/report-2026-01-2026-03/gcc.adoc b/website/content/en/status/report-2026-01-2026-03/gcc.adoc new file mode 100644 index 0000000000..8fb286150a --- /dev/null +++ b/website/content/en/status/report-2026-01-2026-03/gcc.adoc @@ -0,0 +1,25 @@ +=== GCC on FreeBSD + +Links: + +link:https://gcc.gnu.org/[GCC Project] URL: link:https://gcc.gnu.org/[] + +link:https://gcc.gnu.org/gcc-13/[GCC 13 release series] URL: link:https://gcc.gnu.org/gcc-13/[] + +link:https://gcc.gnu.org/gcc-14/[GCC 14 release series] URL: link:https://gcc.gnu.org/gcc-14/[] + +link:https://gcc.gnu.org/gcc-15/[GCC 15 release series] URL: link:https://gcc.gnu.org/gcc-15/[] + +link:https://gcc.gnu.org/gcc-16/[GCC 16 release series] URL: link:https://gcc.gnu.org/gcc-16/[] + + +Contact: Lorenzo Salvadore + +This quarter we have three main pieces of news. + +In January we investigated why GCC 16 weekly snapshots stopped compiling since the last snapshot of November. +It took many eyes to understand what happened, but eventually the problem was understood and a fix was committed upstream in February. +The details can be found in the link:https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123366[upstream bug report]. +Thanks to all people who helped, in particular to Mark Millard and mailto:dim@FreeBSD.org[Dimitry Andric]. + +At the moment package:lang/gcc16-devel[] does not build on arm64. +Unfortunately I have not found the time to really look into this yet, but I hope to be able to do it soon. +link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294062[PR 294062] is the bug report that tracks the issue. + +The link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292692[process] to get GCC_DEFAULT=15 has started. +The GCC_DEFAULT=14 update is still recent and GCC 14 is actively supported, so there is no hurry to get this completed; but since those updates tend to be long I have already started it. +Thus this is not my top priority at the moment: it is is where I put my energy when I have spare cycles, for now.