mortbopet/ripes

A graphical processor simulator and assembly editor for the RISC-V ISA

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 19 minutes ago
Added to GitGenius on September 20th, 2026
Created on October 27th, 2017
Open Issues & Pull Requests: 88 (+0)
GitHub issues: Enabled
Number of forks: 373
Total Stargazers: 3,421 (+0)
Total Subscribers: 44 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 25
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 698 days
Stale 30+ days: 25
Stale 90+ days: 23

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (3)
  • good first issue (3)
  • help wanted (3)
  • WASM (1)
  • bug (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Ripes is a graphical processor simulator and assembly editor for the RISC-V instruction set architecture.

Ripes addresses the challenge of understanding how processors execute code and how architectural decisions affect performance. It provides a visual environment where users can write or load RISC-V assembly code and observe its execution across different microarchitectures. The tool simulates various processor designs based on RV32IMC and RV64IMC variants, allowing exploration of how cache designs influence performance, how C code compiles to assembly, and how processors interact with memory-mapped I/O.

The tool suits educators and students learning computer architecture, as well as anyone needing to understand RISC-V instruction execution in detail. It works best for projects focused on RISC-V development and education rather than production systems. Ripes is available as native applications for Linux, Windows, and macOS, and also runs directly in a web browser through a WebAssembly deployment, making it accessible without installation.

The project maintains active build pipelines across multiple platforms and deployment targets. The maintainers engage with users through a dedicated discussions page for feature requests and ideas, and actively track bug reports through the issues page. Documentation is provided through an introduction tutorial and comprehensive reference materials.