This repository contains an implementation of the CHERIoT ISA in Sail. It contains an executable description of the CHERIoT instruction set that can be used to build an instruction set emulator and also prove properties of the ISA using Sail's SMT support. A full description of the ISA, including extracts from this repository, can be found in the CHERIoT technical report.
The code is dervied from sail-cheri-riscv and uses the sail-riscv model as a submodule.
The easiest way to use this emulator is to use the dev container for the CHERIoT RTOS.
Alternatively, if you wish to build from source you must first install dependencies, including Sail. For example, on Ubuntu 20.04 we have tested:
sudo apt update
sudo apt install opam z3 libgmp-dev
opam init
opam install sail
Then clone the repo:
git clone --recurse-submodules https://github.com/microsoft/cheriot-sail
cd cheriot-sail
Finally build the C emulator:
make csim
This will produce an executable in c_emulator/cheriot_sim that can be used to run ELF files produced by the CHERIoT compiler.
To build the documentation you must have biber, latexmk and pdflatex and have setup your opam environment as above. Then follow the following commands:
pushd archdoc
make
popdThis will create a file located at archdoc/cheriot-architecture.pdf.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.