Date: Wed, 1 Jan 2025 14:04:22 GMT From: Lorenzo Salvadore <salvadore@FreeBSD.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org Subject: git: fd671ff46e - main - Status/2024Q4/gcc.adoc: Add report Message-ID: <202501011404.501E4M8i078520@gitrepo.freebsd.org>
next in thread | raw e-mail | index | archive | help
The branch main has been updated by salvadore: URL: https://cgit.FreeBSD.org/doc/commit/?id=fd671ff46edfa804036c134e5d83fd632cbc032b commit fd671ff46edfa804036c134e5d83fd632cbc032b Author: Lorenzo Salvadore <salvadore@FreeBSD.org> AuthorDate: 2025-01-01 14:03:07 +0000 Commit: Lorenzo Salvadore <salvadore@FreeBSD.org> CommitDate: 2025-01-01 14:03:07 +0000 Status/2024Q4/gcc.adoc: Add report Reviewed by: status (Pau Amma <pauamma@gundo.com>) Pull Request: https://github.com/freebsd/freebsd-doc/pull/451 --- .../en/status/report-2024-10-2024-12/gcc.adoc | 26 ++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/website/content/en/status/report-2024-10-2024-12/gcc.adoc b/website/content/en/status/report-2024-10-2024-12/gcc.adoc new file mode 100644 index 0000000000..a278ac71c0 --- /dev/null +++ b/website/content/en/status/report-2024-10-2024-12/gcc.adoc @@ -0,0 +1,26 @@ +=== GCC on FreeBSD + +Links: + +link:https://gcc.gnu.org/[GCC Project] URL: link:https://gcc.gnu.org/[] + +link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[] + +link:https://gcc.gnu.org/gcc-12/[GCC 12 release series] URL: link:https://gcc.gnu.org/gcc-12/[] + +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/[] + + +Contact: Lorenzo Salvadore <salvadore@FreeBSD.org> + +The link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281091[exp-run to update GCC default version from 13 to 14] is getting forward. +As usual, thanks to everyone involved. + +If you maintain any of the affected ports or want to give a hand preparing and testing some patches, you can consider trying adding `-fpermissive` to `CFLAGS` in affected ports as a temporary solution: GCC 14 has transformed some warnings into errors, which is the cause of many of the failed builds. +The `-fpermissive` flag switches those errors back to warnings. +However, it is preferable that upstream updates its code to remove those warnings completely so that `-fpermissive` is not necessary, possibily with FreeBSD ports maintainers support. +If the code is not maintained upstream anymore, the time might have come to deprecate the port. + +Work has been done on some bugs too, mainly upstream: +- link:https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117210[] has been fixed: a recent change in the FreeBSD headers caused a regression in the GCC 15 development version; +- link:https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115008[] has been fixed: this was an issue with posix_fallocate failing on FreeBSD on a ZFS filesystem; +- an attempt to fix bug link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282797[] specific to aarch64 for -devel ports has failed. +If you are able to give a hand on this, it would be very much appreciated. + +Thanks to everyone who has helped with these issues.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202501011404.501E4M8i078520>