-
Notifications
You must be signed in to change notification settings - Fork 447
RISC V Software Projects
This page contains a list of software projects that need to get done and that are related to RISC-V. If you're looking to get started with RISC-V software development, picking a small project from this list would be a good place to start. It's recommended that you contact the software mailing list sw-dev@lists.riscv.org before starting, just to ensure that this entry is up to date.
Projects in this list are expected to take less than a week for someone familiar with the sort of work that needs to be done. Since these projects are small enough to get done accidentally, it's best to check with the mailing list (or poke around http://github.com/riscv/ to see if there's a port in progress) before starting them to make sure they haven't already been done. If you're confused as to exactly what needs to be done, contacting sw-dev@lists.riscv.org is probably the right thing to do -- all these projects are designed to be closed-ended.
Status: unclaimed
GCC contains a library to do stack tracing that hasn't been ported to RISC-V.
Status: unclaimed
This is required for google-perftools, a profiling tool.
Status: unclaimed
The RISC-V driver model advocates that the SEE only exposes virtualized devices to the supervisor, but spike currently emulates real hardware devices. The result is that the RISC-V Linux port contains HTIF code, which really shouldn't be there.
Status: see Martin Maas maas@eecs.berkeley.edu
Building a frame buffer driver to use the Zedboard's HDMI output
Projects in this list are expected to take more than a week. Since beginning one of these projects is a big task, it would be best to synchronize with the mailing list to see if anyone else interested in is working on the project before attempting to start it on your own.
Status: unclaimed
We don't have a web browser that works on RISC-V. Porting Mozilla will be a big project, since it contains lots of JITs that will need to be targeted to RISC-V.
Status: unclaimed
LLVM contains a linker, but we haven't ported it to RISC-V yet. Since our port of GNU's ld is actually fairly complicated (we use linker relaxations aggressively), this is a fairly intensive project.
Status: In progress, see Michael Knyszek mknyszek@berkeley.edu
Zero interpreter is up and running, template interpreter is being ported.
Status: unclaimed, see Palmer Dabbelt palmer.dabbelt@eecs.berkeley.edu
The Mesa OpenGL rendering library uses LLVM to optimize graphics routines. We'd like to port this to RISC-V so we can benchmarks graphics applications on our implementations.
Status: unclaimed, see Palmer Dabbelt palmer.dabbelt@eecs.berkeley.edu
There is no optimized BLAS for RISC-V, this looks like the best one to port.
Status: some initial progress, ask Martin Maas maas@eecs.berkeley.edu
We'd like to have a port of FreeRTOS for RISC-V.