Show HN: Fursoy – Out-of-order RV64IMAFDV core in SystemVerilog (Linux 6.6)
fursoy
74 points
26 comments
November 14, 2026
Related Discussions
Found 5 related stories in 149.9ms across 12,728 title embeddings via pgvector HNSW
- Show HN: A tiny LLM running at 21,000 tok/s on a $250 FPGA (Live Demo) mikeayles · 12 pts · August 10, 2026 · 52% similar
- Show HN: Our space game has a built-in RISC-V emulator that runs Linux nor-and-or-not · 18 pts · October 02, 2026 · 50% similar
- Show HN: Reame – a CPU inference server that gets faster as it runs targetbridge · 48 pts · July 11, 2026 · 48% similar
- Show HN: Running 104GB Qwen3.8-Flash-Next on 48GB Mac with at ~12 tok/s carloslfu · 187 pts · September 01, 2026 · 47% similar
- Making a VGA Driver in SystemVerilog derHackerman · 34 pts · October 20, 2026 · 47% similar
Discussion Highlights (4 comments)
fursoy
I built Fursoy Slice-1, a 64-bit out-of-order superscalar RISC-V core (RV64IMAFDV + Zba/Zbb/Zicsr/Zifencei) in SystemVerilog, along with a minimal SoC (5-master crossbar, CLINT, PLIC, 16550 UART, and custom SBI v2.0 firmware). At a high level, the core is 2-wide fetch/decode/rename/retire with a 128-entry ROB, 160-entry integer PRF, 8 branch checkpoints for single-cycle speculative RAT rollback, and separate Int/Mem/FP/Vec issue queues. On the memory side, it has a dual-port Sv39 DTLB (64-entry 4-way Tree-PLRU + 8-entry 2 MiB/1 GiB superpage CAM), ITLB, and a 16 KiB 8-bank non-blocking L1D. Instead of flushing dirty lines on every page-table walk, the hardware PTW snoops dirty L1D sets non-destructively so Linux page-table updates are visible directly, paired with store-queue drain on SFENCE.VMA. In Verilator, it boots mainline Linux 6.6.50 and BusyBox userspace in ~89.8M cycles (~76.2M retired instructions, 2,255 page faults handled) while checking an 8-bucket single-owner CPI conservation invariant every cycle with 0 cycle leakage. Synthesizing the 8 main core logic blocks standalone with sv2v + Yosys + OpenSTA on Nangate 45nm (SRAMs/PRFs black-boxed, pre-P&R) meets 500 MHz across all 8/8 blocks at ~219 kGE, after rebuilding the ALU and branch unit as Kogge-Stone prefix trees and balancing high-fanout CSR/TLB paths. I used an AI-agent-assisted workflow for RTL iteration and verification scaffolding while driving the microarchitecture, timing closure, and debugging myself. The nastiest late bug was a Linux boot livelock around ~90M cycles: per RISC-V Priv Spec §3.1.9, CSR read-modify-write instructions on `mip` have to operate on the software-writable `mip_q[9]` bit rather than the live `irq_seip_i` wire—our CSR block was feeding `mip_val` back into RMW, so whenever SBI cleared `STIP` while a PLIC IRQ was high, it permanently latched `SEIP` and trapped the kernel in `plic_handle_irq`. For folks who have built Sv39 cores or open-source ASIC flows: do you prefer letting the PTW snoop dirty L1D lines directly like this, or forcing a clean/drain path? Also curious what people would tackle next on a single-core tree like this—an inclusive L2 cache or jumping straight to dual-core coherency.
Findecanor
Do post it on Reddit in https://www.reddit.com/r/RISCV/ I have seen more excitement and community around these kinds of projects there than here.
phendrenad2
Doing OOO in a one-person project is impressive.
PowerElectronix
This is really cool. Any chance you'll try to make a few with tiny tap or some service like that?