Arm has dominated the mobile space since the dawn of smartphones, but systems based on the open source RISC-V instruction set architecture will bring new choices for manufacturers and us, their customers. RISC-V SDKs showed up in the Dart dev channel in Apr 22, but it's still pretty hard to build stuff due to lots of missing dependencies. As always happens with new stuff, the hardware people are waiting for broader software support, and the software people are waiting for a larger hardware installed base. This talk examines the forces that are driving RISC-V forward, and what developers can expect from a world that will have RISC-V devices, mobile phones, tablets and cloud services.
34. Android Profiles
Supported ABI will be added to the CDD list as riscv64 (no 32bit)
All “supported instruction sets” will be a combination of:
● A RISC-V profile (probably RVA22)
● Ratified extensions (probably vector + vector crypto)
● Intentional omissions: SIMD, Scalar Crypto
Will require Android compatible devices to be conforming hardware
● Must correctly implement the RISC-V ISA
● Must not misuse elements of the encoding space reserved for future extensions
Platforms (but not applications) can take advantage of the RISC-V features in the
reserved vendor space