Key Takeaways
- Linux kernel developers plan to remove the x32 ABI by 2027 due to low adoption
- The hybrid mode was introduced in 2012 to reduce memory usage but never caught on
- Removal will free up 40 system call slots for future x86_64 development
Sebastian Andrzej Siewior, a kernel developer at Linutronix, has proposed removing the x32 ABI from the Linux kernel. If no objections arise, the 14-year-old hybrid mode will be gone by 2027.
The x32 ABI was an interesting experiment. It let 64-bit processors run programs with access to full 64-bit registers while using 32-bit pointers. The idea was simple: cut pointer sizes in half, fit more data in CPU caches, and get better performance without the memory overhead of pure 64-bit operation.
It didn't work out that way.
What x32 ABI Was Supposed to Do
When x32 ABI landed in Linux kernel version 3.4 back in 2012, memory was more expensive and caches were smaller. A pointer in pure 64-bit mode takes 8 bytes. In x32 mode, it takes 4 bytes. For programs that juggle millions of pointers, that's real savings.
The hybrid approach let programs use the full 64-bit instruction set and registers. They got access to all those extra CPU features while keeping a smaller memory footprint. Testing showed 5 to 10 percent performance improvements in specific workloads.
But there was a catch. Actually, several catches.
Why It Never Caught On
The 32-bit pointer size created a hard ceiling. Individual processes using x32 ABI could not address more than 4GB of memory. In 2012, that seemed like plenty for most applications. By 2015, it was becoming a real limitation. By 2020, it was a dealbreaker for many use cases.
“This approach did not catch on... memory usage usually knows no bounds and even performance improvements did not help to get the whole thing to a point where certain types of tasks would move to x32 on a large scale.”
— Sebastian Andrzej Siewior, Linux Kernel Developer at Linutronix
The ABI also required special compiler support and added complexity for developers. Building software for x32 meant maintaining another target alongside regular 32-bit and 64-bit builds. Most developers decided the 5 to 10 percent performance gain wasn't worth the extra work.
Perhaps the biggest problem: x32 ABI was Linux-only. Windows and macOS never implemented it. That meant cross-platform software couldn't rely on it, which meant most software ignored it entirely.
The Cost of Keeping It Around
Legacy code doesn't sit quietly in a kernel. It needs testing, maintenance, and sometimes blocks other work. The x32 ABI currently occupies 40 system call slots that kernel developers could use for new features. That's not a trivial amount of the available address space.
Every kernel release requires testing x32 compatibility. Every new feature needs to consider x32 implications. For a mode that almost nobody uses, that's a lot of overhead.
Community Response
Discussion on Hacker News and Reddit has been largely supportive. Most developers agree the removal is overdue. The maintenance burden clearly outweighs the benefits for such a small user base.
Some niche users will miss it. Certain Gentoo users and high-performance computing enthusiasts have found value in the memory savings over the years. But even many of them acknowledge that the broader Linux ecosystem is better served by cleaning up this technical debt.
The 2027 timeline gives anyone still relying on x32 ABI roughly two years to migrate. That's reasonable for such a niche feature.
What Happens Next
The proposal is now in the objection period. If kernel maintainers and the broader community don't raise significant concerns, the removal will proceed. Based on the reaction so far, that seems likely.
For most Linux users, nothing changes. If you're running a modern distribution, you're almost certainly using pure 64-bit mode already. The x32 ABI will quietly disappear, and the kernel will be slightly simpler for it.
Logicity's Take
Frequently Asked Questions
What is the x32 ABI in Linux?
The x32 ABI is a hybrid application binary interface that lets 64-bit processors run programs using 32-bit pointers. It was designed to reduce memory usage while keeping access to 64-bit registers and instructions.
Why is Linux removing the x32 ABI?
The x32 ABI never gained mainstream adoption. It adds maintenance burden to the kernel, blocks 40 system call slots, and requires ongoing testing for a feature almost nobody uses.
Will removing x32 ABI affect my Linux system?
For almost all users, no. Modern Linux distributions use pure 64-bit mode by default. Only a small number of specialized users in HPC or Gentoo communities have relied on x32.
When will the x32 ABI be removed from Linux?
If no major objections are raised to the current proposal, the x32 ABI will be removed by 2027, giving it a total lifespan of about 14 years.
For more on hardware economics and technical tradeoffs
Need Help Implementing This?
Source: Latest from Tom's Hardware
Manaal Khan
Tech & Innovation Writer
Produced with AI assistance and reviewed by the Logicity editorial team. Learn more in our Editorial Policy.
