HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
riscv
sail-riscv
Sail2021–2025
riscv / sail-riscv

sail-riscv

Sail RISC-V model

7Distinct people
12Mentions
0Explicit recommenders
807GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Sail RISC-V model

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 6:28:55 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year12 dated mentions

Observed mentions: 2021-12-02 18:11:02 UTC to 2025-11-05 14:06:36 UTC.

0123452021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC505
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC413

What Hacker News says

4 sources
Another way to build emulators that I am very interested in is to start from a spec, and automatically translate it into executable code. High-fidelity emulators have a lot of potential for testing and verification. The best example I know of is Sail [1]. Among other, they have RISC-V spec [2] and a bunch of compiler back-ends. They can already generate C or OCaml emulators, and I have been working on a new Rust back-end recently. [1]: https://github.com/rems-project/sail [2]: https://github.com/riscv/sail-riscv
In Writing a RISC-V Emulator in Rust
I've used this a lot via the RISC-V Sail model: https://github.com/riscv/sail-riscv It's a really nice language - especially the lightweight dependent types. Basically it has dependent types for integers and bit-vector lengths so you can have some really nice guarantees. E.g. in this example https://github.com/Timmmm/sail_demo/blob/master/src/079_page... we have this function type val splitAccessWidths : forall 'w, 0 <= 'w . (xlenbits, int('w)) -> {'w0 'w1, 'w0 >= 0 & 'w1 >= 0 & 'w0 + 'w1 == 'w . (int('w0), int('w1))} Which basically means it returns a tuple of 2 integers, and they must sum to the input integer. The type system knows this. Then when we do this: let (width0, width1) = splitAccessWidths(vaddr, width); let val0 = mem_read_contiguous(paddr0, width0); let val1 = mem_read_contiguous(paddr1, width1); val1 @ val0
Read the rest
The type system knows that `length(val0) + length(val1) == width`. When you concatenate them (@ is bit-vector concatenation; wouldn't have been my choice but it's heavily OCaml-inspired), the type system knows `length(val1 @ val0) == width`. If you make a mistake and do `val1 @ val1` for example you'll get a type error. A simpler example is https://github.com/Timmmm/sail_demo/blob/master/src/070_fanc... The type `val count_ones : forall 'n, 'n >= 0. (bits('n)) -> range(0, 'n)` means that it's generic over any length of bit vector and the return type is an integer from 0 to the length of the bit vector. I added it to Godbolt (slightly old version though) so you can try it out there. It's not a general purpose language so it's really only useful for modelling hardware.
In The Sail instruction-set semantics specification language
charlycst·May 10, 2025Submission

Show HN: Miralis – a RISC-V virtual firmware monitor

Miralis is a RISC-V firmware that virtualizes RISC-V firmware. In other words, it runs firmware in user-space (M-mode software in U-mode). The fact that this is even possible is interesting: indeed, not all ISAs are virtualizable, and the same applies for their firmware mode. It all boils down to the virtualization requirements [1], which is a great read if you haven't come across it yet. Arm's EL3 cannot be virtualized, for instance, because some instructions, such as `cpsid`, are sensitive but do not trap (`cpsid` is a nop in user-space). If you have a VisionFive 2 or a HiFive Premier P550, you can try it out, the instructions are in the documentation [2, 3]. Of course, it runs on QEMU too. As Miralis is a research project, we have also been using it as a vehicle to explore other research ideas, such as automated verification of hypervi
Read the rest
sors [4]. For instance, we verified instruction emulation by comparing Miralis' implementation with the reference RISC-V executable specification [5], which we translated to Rust. It has been fun working on Miralis, I hope you'll find it interesting too! [1]: https://dl.acm.org/doi/pdf/10.1145/361011.361073 [2]: https://miralis-firmware.github.io/docs/platforms/visionfive... [3]: https://miralis-firmware.github.io/docs/platforms/premierp55... [4]: https://charlycst.github.io/papers/lightweight-hypervisor-ve... [5]: https://github.com/riscv/sail-riscv
4 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.