.githooks/
riscv/
test/
.clang-format
570 B
.gitignore
5 B
.gitsigners
112 B
AGENTS.md
227 B
LICENSE
1.1 KiB
Makefile
3.5 KiB
README
12.5 KiB
STYLE
781 B
abi_host.c
12.2 KiB
abi_linux.c
3.7 KiB
bitmanip.h
5.8 KiB
color.h
567 B
debug_map.c
5.1 KiB
debug_map.h
1.3 KiB
emulator.c
87.3 KiB
host.h
5.5 KiB
host_posix.c
11.2 KiB
hosted.h
5.7 KiB
image_native.c
4.6 KiB
image_rad0.c
2.7 KiB
image_raw.c
2.6 KiB
io.c
1.1 KiB
io.h
444 B
jit.c
99.2 KiB
jit.h
7.8 KiB
machine.c
4.4 KiB
machine.h
2.1 KiB
machine_cpu.c
13.6 KiB
machine_csr.c
4.6 KiB
machine_devices.c
10.8 KiB
machine_fdt.c
8.7 KiB
machine_internal.h
7.4 KiB
muldiv.h
1.0 KiB
profile.c
17.5 KiB
profile.h
1.4 KiB
riscv.c
755 B
riscv.h
4.3 KiB
types.h
1019 B
vector.c
54.0 KiB
vector.h
1.3 KiB
STYLE
raw
| 1 | * Separate function definitions with a blank line. If a function has a |
| 2 | comment, put the blank line before the comment. |
| 3 | * Groups of function prototypes do not need blank lines between them or |
| 4 | before their comments. |
| 5 | * Put standard and system headers first. Put third-party headers next, |
| 6 | followed by project headers. Separate these groups with a blank line. |
| 7 | * Include project headers with quotes. Use paths relative to the source |
| 8 | directory or the project root. Do not use parent directory components. |
| 9 | * Use short, clear variable and field names. Avoid names that make |
| 10 | declarations difficult to align. |
| 11 | * Keep struct fields and their comments aligned. Keep trailing comments |
| 12 | short. Put longer comments above the fields they describe. Make sure struct |
| 13 | fields align after formatting. |