ports/lang/gcc12, branch main FreeBSD ports tree */*: Use C.UTF-8 locale 2026-06-30T20:03:57+00:00 Tijl Coosemans tijl@FreeBSD.org 2026-06-07T16:50:32+00:00 b6ec06f079e1c883d32c788c0285c6d492eeb1c0 Ports 02f27a83b44d fixed the ports tree to the C locale so it would work correctly in environments where users use a locale that isn't compatible with the C locale, e.g. xx_YY.UTF-8 where [A-Z] includes more than just upper case letters. USE_LOCALE was introduced to let ports use another locale if they needed it. The C.UTF-8 locale was created later on to be mostly compatible with the C locale. Switch the ports tree locale to C.UTF-8 and remove USE_LOCALE. The world has moved to Unicode so all ports either require it or know how to build correctly in a Unicode environment. PR: 295945 Exp-run by: antoine 
Ports 02f27a83b44d fixed the ports tree to the C locale so it would work
correctly in environments where users use a locale that isn't compatible
with the C locale, e.g. xx_YY.UTF-8 where [A-Z] includes more than just
upper case letters.  USE_LOCALE was introduced to let ports use another
locale if they needed it.  The C.UTF-8 locale was created later on to be
mostly compatible with the C locale.

Switch the ports tree locale to C.UTF-8 and remove USE_LOCALE.  The
world has moved to Unicode so all ports either require it or know how to
build correctly in a Unicode environment.

PR:		295945
Exp-run by:	antoine
lang/gcc1[2-6]: actually fix build on powerpc64le/CURRENT 2026-06-27T20:55:24+00:00 Piotr Kubaj pkubaj@FreeBSD.org 2026-06-27T20:53:18+00:00 70f1f8cf7762db8fe6648bff3436cc604507d494 Without this patch, gcc attempts to enable support for IBM long double, when IEEE long double is enabled, which is wrong. Allow to only specify IEEE long double. The whole patchset for IEEE long double on FreeBSD/powerpc64le is being upstreamed at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=126012. 
Without this patch, gcc attempts to enable support for IBM long double,
when IEEE long double is enabled, which is wrong. Allow to only
specify IEEE long double.

The whole patchset for IEEE long double on FreeBSD/powerpc64le
is being upstreamed at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=126012.
lang/gcc1[2-6]: add necessary contents to patch-gcc_configure 2026-06-21T20:48:49+00:00 Piotr Kubaj pkubaj@FreeBSD.org 2026-06-21T20:46:16+00:00 35a12271a3ee93d0e2e4fc6a742b927fccc721f9 1. For gcc14, restore the lost content. 2. For others, add powerpc64le-related content. Pointy hat: me 
1. For gcc14, restore the lost content.
2. For others, add powerpc64le-related content.

Pointy hat:	me
lang/gcc1?: fix runtime on powerpc64le/CURRENT 2026-06-21T20:05:23+00:00 Piotr Kubaj pkubaj@FreeBSD.org 2026-06-21T20:01:35+00:00 c02c1227e2d23dbfdb7a4b32cc29f42847a21cfd Since powerpc64le recently switched to 128-bit long double, use them to generate proper binaries. Patches are necessary to allow use of --with-long-double-format=ieee on FreeBSD (to be upstreamed). 
Since powerpc64le recently switched to 128-bit long double, use them to
generate proper binaries. Patches are necessary to allow use of
--with-long-double-format=ieee on FreeBSD (to be upstreamed).
lang/gcc12: Add comment to existing patch 2025-05-03T09:46:25+00:00 Lorenzo Salvadore salvadore@FreeBSD.org 2025-04-30T14:51:24+00:00 a38818665f79d0455c1b788ff2cfb18c2e19181c Add a comment to files/patch-libgcc_unwind.inc to remember when it will get obsolete, i.e. once all supported FreeBSD releases include commit 22e564c74eb20e14bd93fd9fdde20e38a29cfcf1. PR: 285711 
Add a comment to files/patch-libgcc_unwind.inc to remember when it will
get obsolete, i.e. once all supported FreeBSD releases include commit
22e564c74eb20e14bd93fd9fdde20e38a29cfcf1.

PR:             285711
lang/gcc12: Fix SIGBUS depending on CPUTYPE 2025-04-24T12:55:47+00:00 Oleg Sidorkin osidorkin@gmail.com 2025-04-23T14:36:49+00:00 231018e228187099b8fac7e55b1a662cdc81c1f8 Compiling GCC with some CPUTYPE values (e.g. broadwell) result in breaking some applications (e.g. math/octave, cad/freecad), sending a SIGBUS. The issue is due to GCC generating instructions that require variables to be aligned in memory on certain CPUs. Our libthr does not have the required alignment so these CPUs fail to execute these instructions. The patch disables the generation of such instructions. PR: 285711 Reported by: cracauer Tested by: cracauer, jbo 
Compiling GCC with some CPUTYPE values (e.g. broadwell) result in
breaking some applications (e.g. math/octave, cad/freecad), sending a
SIGBUS.

The issue is due to GCC generating instructions that require variables
to be aligned in memory on certain CPUs. Our libthr does not have the
required alignment so these CPUs fail to execute these instructions.

The patch disables the generation of such instructions.

PR:             285711
Reported by:    cracauer
Tested by:      cracauer, jbo
gcc*: properly define USE_LDCONFIG32 for multilib 2025-03-13T16:54:27+00:00 Baptiste Daroussin bapt@FreeBSD.org 2025-03-13T16:53:55+00:00 13904d7107442b60c6a3403d1fdd94bc13f731af 






lang/gcc12: Fix linking with libisl.so
2025-03-05T15:32:48+00:00

Lorenzo Salvadore
salvadore@FreeBSD.org

2025-03-04T10:29:58+00:00

1846a7fe9b587894845d69a895510f37eb2f40d8

Fix linking with libisl.so depending on GRAPHITE option, which is
now implemented through options helpers.

Co-authored-by: Gerald Pfeifer <gerald@FreeBSD.org>

PR:         276070
Reported by:Ivan Rozhuk <rozhuk.im@gmail.com>





Fix linking with libisl.so depending on GRAPHITE option, which is
now implemented through options helpers.

Co-authored-by: Gerald Pfeifer <gerald@FreeBSD.org>

PR:         276070
Reported by:Ivan Rozhuk <rozhuk.im@gmail.com>







lang/gcc12: Fix segfaults for static binaries
2025-02-10T18:18:05+00:00

Dimitry Andric
dim@FreeBSD.org

2025-02-04T09:08:43+00:00

6f5f51aaee2e3d4b217eebeccc64850b924e414a

Fix segmentation faults caused by -static flag into compiled binaries.

Email thread: https://lists.freebsd.org/archives/freebsd-hackers/2025-January/004236.html
Upstream bug report: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118685

PR:             284441
Reported by:    kargl





Fix segmentation faults caused by -static flag into compiled binaries.

Email thread: https://lists.freebsd.org/archives/freebsd-hackers/2025-January/004236.html
Upstream bug report: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118685

PR:             284441
Reported by:    kargl







lang/gcc*: disable building of libssp
2024-10-29T23:54:20+00:00

Kyle Evans
kevans@FreeBSD.org

2024-10-29T23:52:59+00:00

17024a6f828904fbd57ff459b32f9ed21f77a1a4

For today's FreeBSD 14 and earlier, libssp is a nop because nothing on
FreeBSD will be referencing these headers or lib.  On FreeBSD 15, it
actively breaks building with FORTIFY_SOURCE enabled and it's not worth
trying to make it work- the potential for GCC improvements comes from
the __builtin_object_size enhancement, not from these headers.

PR:		280265
Approved by:	salvadore (maintainer)





For today's FreeBSD 14 and earlier, libssp is a nop because nothing on
FreeBSD will be referencing these headers or lib.  On FreeBSD 15, it
actively breaks building with FORTIFY_SOURCE enabled and it's not worth
trying to make it work- the potential for GCC improvements comes from
the __builtin_object_size enhancement, not from these headers.

PR:		280265
Approved by:	salvadore (maintainer)