3 ms·
Actually, https://github.com/google/android-riscv64?tab=readme-ov-file https://github.com/google/android-riscv64?tab=readme-ov-file And the mailing list is pre
by shash 2y ago
Actually, https://github.com/google/android-riscv64?tab=readme-ov-file https://github.com/google/android-riscv64?tab=readme-ov-file
And the mailing list is pretty active too: https://lists.riscv.org/g/sig-android/topics?sidebar=true https://lists.riscv.org/g/sig-android/topics?sidebar=true
- refulgentis 2y agoI don't know why people keep replying as if I'm saying Android isn't going to do RISC-V. I especially don't understand offering code that predates the removal from tree and hasn't been touched since. Or, a mailing list, where we click on the second link and see a Google employee saying on October 10th "there isn't an Android riscv64 ABI yet either, so it would be hard to have [verify Android runs properly on RISC-V] before an ABI :-)" That's straight from the horses mouth. There's no ABI for RISC-V. Unless you've discovered something truly novel that you left out, you're not compiling C that'll run on RISC-V if it makes any system calls. I assume there's some psychology thing going on where my 110% correct claim that it doesn't run on RISC-V today is transmutated to "lol risc-v doesn't matter and Android has 0 plans" I thoroughly believe Android will fully support RISC-V sooner rather than later.