Linux Developers Looking At Retiring The x32 ABI
Linux developers are considering the retirement of the x32 ABI, which was introduced to optimize memory usage on x86_64 processors. The x32 ABI has seen limited adoption since its introduction in 2012, leading to discussions about its removal from the Linux kernel. If the proposal goes through, 2026 may mark the end of the x32 ABI.
- ▪The x32 ABI was designed to use 32-bit pointers while leveraging 64-bit capabilities.
- ▪Limited adoption has led to concerns about its relevance in modern computing.
- ▪Debian and Fedora have disabled x32 by default due to security concerns.
2 outlets in our directory ran this story, first to last over 3 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ Linux Developers Looking At Retiring The x32 ABI — r/linux
Phoronix files mainly under tech. We currently carry 191 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Phoronix |
| Canonical URL | https://www.phoronix.com/news/Linux-x32-ABI-2026 |
| Publication time | Wed, 27 May 2026 08:53:58 -0400 |
| Retrieval time | 2026-05-27T13:03:00.492Z |
| Last seen | 2026-05-27T13:03:00.492Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 9qF6k-f5xNRY · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Linux Developers Looking At Retiring The x32 ABI Written by Michael Larabel in Linux Kernel on 27 May 2026 at 08:53 AM EDT. Add A Comment The Linux x32 ABI for x86_64 processors allow making use of the full 64-bit register file and wide data path but retaining 32-bit pointers to provide for a smaller memory footprint when not needing 64-bit pointers. Linux x32 came to the party late and didn't enjoy much adoption over the years and is now looking at possible removal from the Linux kernel. The x32 code was a nice concept for helping lower memory footprint requirements while otherwise making use of the x86_64 capabilities, but with its limited adoption and x86_64 simply being the de facto standard these days, Linux kernel developers are looking at phasing out the x32 ABI.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Phoronix.