Some customers are still stuck in a world of 32bit. On ARM64, we have two options for those poor folks:
1) Run applications in the legacy ARMv7 instruction set 2) Compile applications with 32bit, but for the new AArch64 instruction set. This is called ILP32.
The main reason option 1 is a bad idea is that some hardware is already dropping ARMv7 instruction set support. And there will be more to come.
So if we ever want to enable people to run code that is not 64bit safe on AArch64 platforms, we need to provide them with a way out. Hence we should bootstrap at least the bare minimum to enable them to compile their own (broken) code.
Beware that all of this is in a big flux. The interfaces (ABI, syscalls) are not yet set in stone.
This project is part of:
Hack Week 12
Activity
Comments
Be the first to comment!
Similar Projects
Create a DRM driver for VGA video cards by tdz
Yes, those [VGA video cards](https://en.wikiped...
Hacking on sched_ext by flonnegren
Description
Sched_ext upstream has some i...
Linux on Cavium CN23XX cards by tsbogend
Before Cavium switched to ARM64 CPUs they devel...
Kill DMA and DMA32 memory zones by ptesarik
Description
Provide a better allocator fo...
Officially Become a Kernel Hacker! by m.crivellari
Description
My studies as well my spare tim...
Improve various phones kernel mainline support (Qualcomm, Exynos, MediaTek) by pvorel
Similar to previous hackweeks ( [https://hackwe...
Research openqa-trigger-from-obs and openqa-trigger-from-ibs-plugin by qwang
Description
openqa-trigger-from-obs project...
Automation of ABI compatibility checks by ateixeira
Description
ABI compatibility checks could ...
Git CI to automate the creation of product definition by gyribeiro
Description
Automate the creation of produc...
Learn obs/ibs sync tool by xlai
Description
Once images/repo are built from...
Testing and adding GNU/Linux distributions on Uyuni by juliogonzalezgil
Join the Gitter channel! [https://gitter.im/uy...