On 2026-10-26 10:11 a.m., Kirill A. Korinsky wrote:
On Mon, 26 Oct 2026 13:25:15 +0100,
Brad Smith <[email protected]> wrote:
On Wed, Oct 14, 2026 at 07:44:50PM -0400, Brad Smith wrote:
Fix various GCC ports on powerpc64 by either renaming the existing
patch since GCC has moved from C to C++ for newer versions or add
the missing patch. For the x86_64-elf port it only builds on amd64
so remove the ununused bits from the Makefile.
Here is rev 2 of this patch.

I have removed the separate vecstep patches and instead integrated
the upstream workaround into system.h. Dropping the separate patches
also removes a fragile piece of the build infrastructure.

I wonder, after I commit your v1 patch to lang/gcc/16, shall we update all
other cross gcc to 16.2.0 and sync used patches?

The microcontroller SDKs vendor GCC in different ways, typically through rolled tarballs or their own patch sets, so they cannot simply be upgraded to an arbitrary GCC version. Some can be moved to newer versions, depending on the target, but
that does not mean they should all be updated to 16.2.0.

It should make port tree cleaner.

It would not make the ports tree cleaner, either. There is no reason to sync
patches from the native host compiler to the cross-compilers. They have
completely different patch sets for different purposes.

Reply via email to