This site is being rebuilt and some pages are out of date. For current details, write to [email protected]. This notice goes away when the rebuild is done.

No analytics unless you allow it, no tracking. This site keeps in your browser the language you pick, the theme, its colour, which site you chose, the currency on the pricing page and that you closed this notice; signing in adds session cookies. The legal page has the details.

Sign in

Radar · Go · Archive · Week 5 · Jan 26 – Feb 1, 2026

Transition ppc64/linux (big‑endian) from ELFv1 to ELFv2 in Go 1.27

Nice to knowecosystem

What changed
The Go team will switch the linux/ppc64 big‑endian port from the ELFv1 ABI to the ELFv2 ABI starting in Go 1.27, with a pre‑announcement in Go 1.26. The change is expected to be transparent because the target does not currently support linking against other ELF objects.
Production impact
The source does not say.
Try it
None applicable for most users; this is a background change for maintainers of the ppc64/linux port.
Source
github.com/golang/go/issues/76244

Understand it, then run it

Run it now

Todaygo
// This program demonstrates that the Go compiler for ppc64/linux
// (big‑endian) still builds and runs on Go 1.27.1, which uses ELFv2.
// It prints a simple message; the ABI switch is transparent to Go code.
package main

import "fmt"

func main() {
	// Print a greeting to show the binary runs.
	fmt.Println("Hello from ppc64/linux big‑endian!")
}

What it printed when we ran it on Go 1.27.1

Hello from ppc64/linux big‑endian!

Run sends this program (for Solidity, the contract and its tests) to our own sandbox, where it is compiled and run once, with no network, and what it printed or the test report comes back here. Nothing is kept. Runs are counted per visitor for the day so everyone gets a turn; the details are on the legal page.

Written by gpt-oss-20b from the linked source · claims checked against the sources · archive, not individually reviewed