Driving Innovation: Evolving the Role of Software in the RISC-V Ecosystem Beyond...
summary
RISC-V software shifts from enablement to driving ISA evolution with concrete results: unified discovery draft and indirect function support in glibc/ld so kernels and userland can detect vendor extensions; upstream paths for vendor extensions and a merged conventions doc for toolchains; nested virtualization validated and optimized OpenSSL patches landing; OpenJDK support merged; qemu reaches ~350–450 MIPS for validation; a 1.2M-line auto-vectorizer submission for GCC under cleanup; platform work split into RVM/CSI for MCUs and OSA for rich OS/binary compatibility.
AI-written summary · about
chapters (13)
- 0:00Introduction to RISC-V software
- 1:25Major RISC-V extensions
- 3:49Software's role in the stack
- 6:16Managing fragmentation in innovation
- 8:00Upstreaming vendor extensions
- 9:48OpenJDK support progress
- 10:29Unified discovery for extensions
- 12:13Auto vectorization in GCC
- 13:15End-to-end performance workflows
- 14:42Domain-specific extensions
- 16:06Android and Linux support
- 17:49Platform standardization efforts
- 19:36Call to join the ecosystem
related talks
23mThe Road Ahead
15mKeynote: Co-Designing Software and Hardware: Pillars of Advancing RISC-V for Application Success
24mRISC-V software ecosystem in 2020
09mKeynote: RISC-V Challenges & Opportunities
21mRISE Technical Steering Committee Update
15mKeynote: From Hardware Innovation to a Thriving RISC-V Ecosystem
19mThe RISE Project: Advancing RISC-V Software
14mRISC-V Spotlight: RISC-V: Everyone Wins
