How denysskobalo/silico works
Project type and purpose
• The README documents ARM general-purpose, special-purpose and status registers, indicating the C code implements or simulates an ARM-like CPU core.
• The Makefile and .gitignore at the root enforce a unified build and versioning strategy for both components.
File structure
• Top-level:
• Makefile – orchestrates building the C library and the Go server (likely via cgo).
• backend/ – Go code; under cmd/server/main.go sits the HTTP server entry point.
• kernel/ – pure C code structured into:
– include/ – header files (types.h, registers.h, cpu.h, flags.h, utils.h, addresses.h) defining data structures and interfaces.
– src/ – implementation modules (cpu.c, utils.c, main.c) that implement CPU behavior.
– archive/ – legacy or experimental C sources (archive/main.c).
• No frontend folder implies the focus is on the backend-service + core library; clients (CLI or web-UI) are external or forthcoming.
README for additional insights
• README is a register reference guide rather than an architecture description, confirming that the “kernel” is really a CPU or emulator core.
Detail is key
• “archive” submodule as a separate component or note it as “legacy code.”
• External dependencies (Go standard library, C standard library).