authorgravatar for alex@alexrp.comAlex Rønne Petersen <alex@alexrp.com> 2026-08-05 13:08:30+02:00
committergravatar for alex@alexrp.comAlex Rønne Petersen <alex@alexrp.com> 2026-08-05 13:28:22+02:00
log143767a05bae7247733b6f03b56d603080a83df7
tree5fb6c2ecb7fcae1655a2c74416fd6598be97e2ca
parent01e5c1885684609d84c79135e716b33a1c3fd9a1
signaturebadge-check Signed by SSH key SHA256:7B/LJ7bpR1eX8aCXSr4mtd5M45VMPKcx9zY8e95b5QM

std.Target: bump baseline CPU for powerpc64-(freebsd,linux) to pwr8

Linux and FreeBSD usage on PowerPC broadly splits into two camps: * Old Apple/Amiga hardware * Modern IBM POWER hardware In the first camp, we're talking hardware like the PowerPC 970 (2002) or even older in some cases. In the second camp, most hardware still in use today is POWER8 (2014) or newer. I think it's safe to say that the first camp is in the minority, especially since the open hardware platform that Raptor Computing Systems sells is based on POWER9, and I expect that to be more interesting to PowerPC enthusiasts nowadays. Also, compiler support for the old hardware is poorly maintained. IBM themselves only seem to care to support the newer POWER processors in the Linux kernel as well as GCC and LLVM. We keep running into LLVM bugs when targeting those older CPUs.

1 files changed, 1 insertions(+), 0 deletions(-)

lib/std/Target.zig+1
......@@ -2081,6 +2081,7 @@ pub const Cpu = struct {
20812081 else => generic(arch),
20822082 },
20832083 .powerpc64 => switch (os.tag) {
2084 .linux, .freebsd => &powerpc.cpu.pwr8,
20842085 .openbsd => &powerpc.cpu.pwr9,
20852086 else => generic(arch),
20862087 },