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.

Looking for mad skills in:

arm ilp32 binutils kernel aarch64 obs openbuildservice

This project is part of:

Hack Week 12

Activity

  • almost 4 years ago: a_faerber left [ARM] Bootstrap ILP32 on AArch64
  • almost 4 years ago: a_faerber added keyword "openbuildservice" to [ARM] Bootstrap ILP32 on AArch64
  • almost 4 years ago: a_faerber added keyword "obs" to [ARM] Bootstrap ILP32 on AArch64
  • almost 4 years ago: a_faerber liked [ARM] Bootstrap ILP32 on AArch64
  • almost 4 years ago: a_faerber joined [ARM] Bootstrap ILP32 on AArch64
  • Show History

    Comments

    Be the first to comment!

    Similar Projects

    Make Tumbleweed work on the GPD Win by aplazas

    The GPD Win is a Nintendo 3DS XL sized PC featu...


    Make Intel baytrail based device(s) work better with openSUSE by mkubecek

    Recently I became a (not very proud) owner of A...


    Base container image and template for openSUSE Leap 42.3 by dmacvicar

    Build a base image and template (both kiwi and ...


    Persona openid for Build Service by k0da

    Build Service needs an openid.

    Imagine follo...


    Cuddle the i2c-i801 kernel driver by jdelvare

    The i2c-i801 kernel driver (for SMBus controlle...