From e47951745d049ff0a91848e5f88e0e0363f48259 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Rom=C3=A1n=20C=C3=A1rdenas=20Rodr=C3=ADguez?= Date: Sat, 11 Jan 2025 13:14:13 +0100 Subject: [PATCH] RFC template for nominating CSRs to be write-safe --- ...riscv---nominate-csr-to-be--write--safe.md | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/-riscv---nominate-csr-to-be--write--safe.md diff --git a/.github/ISSUE_TEMPLATE/-riscv---nominate-csr-to-be--write--safe.md b/.github/ISSUE_TEMPLATE/-riscv---nominate-csr-to-be--write--safe.md new file mode 100644 index 00000000..7362a314 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/-riscv---nominate-csr-to-be--write--safe.md @@ -0,0 +1,23 @@ +--- +name: "`riscv`: Nominate CSR to be `write` safe" +about: Suggest to make writes of a given CSR safe +title: "`riscv`: make [CSR] write-safe" +labels: '' +assignees: '' + +--- + +**Which CSR do you want to nominate as `write` safe?** +Indicate which CSR you want to be `write` safe. Ex. `mepc` + +**Does a CSR write introduce potential memory safety issues in safe code? Please describe.** +A clear and concise justification on why writing to this CSR will **never** introduce memory safety issues in safe code. + +**Does a CSR write introduce potential undefined behavior in safe code? Please describe.** +A clear and concise justification on why writing to this CSR will **never** lead to undefined behavior in safe code. + +**Does a CSR write invalidate invariants in safe code?** +A clear and concise justification on why writing to this CSR will **never** invalidate invariants in safe code. + +**Additional context** +Please feel free to add any other context or screenshots about your request here.