diff options
| author | DymShanks <166487860+DymShanks@users.noreply.github.com> | 2026-01-30 02:44:38 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-01-29 13:14:38 -0800 |
| commit | 3a301b3d7faef3b97163adb5797074b7024fcf95 (patch) | |
| tree | 91844eaa477e74ddb7baa6aed1b7b3d43c184753 | |
| parent | 451f8bd162b80e17a01fc0541dfb382c743dcf9b (diff) | |
| download | riscv-opcodes-master.zip riscv-opcodes-master.tar.gz riscv-opcodes-master.tar.bz2 | |
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -37,7 +37,7 @@ When an instruction is present in multiple extensions and the spec is vague in d ## Encoding Syntax -The encoding syntax uses `$` to indicate keywords. As of now 2 keywords have been identified : `$import` and `$pseudo_op` (described below). The syntax also uses `::` as a means to define the relationship between extension and instruction. `..` is used to defined bit ranges. We use `#` to define comments in the files. All comments must be in a separate line. In-line comments are not supported. +The encoding syntax uses `$` to indicate keywords. As of now 2 keywords have been identified : `$import` and `$pseudo_op` (described below). The syntax also uses `::` as a means to define the relationship between extension and instruction. `..` is used to define bit ranges. We use `#` to define comments in the files. All comments must be in a separate line. In-line comments are not supported. Instruction syntaxes used in this project are broadly categorized into three: |