Refactor VM memory to support sections
Open
enhancement
- Dominant language
- C
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
At the moment, the memory of the VM is shared between code and data (I put the data after a `RK_HALT` instruction).
Supporting separate sections (`.text`, `.data`, `.bss`) would be better.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how the VM currently represents shared memory and how code, data, and the RK_HALT marker are laid out. Define separate .text, .data, and .bss sections, then verify that VM execution and data access use the intended section boundaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100