| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 4621 | Kartik Agaram | 2018-09-30 | 1 | -15/+33 |
| | | | | | Error messages if we ever get segments messed up. | ||||
| * | 4617 | Kartik Agaram | 2018-09-29 | 1 | -2/+5 |
| | | |||||
| * | 4614 - redo simulated RAM | Kartik Agaram | 2018-09-29 | 1 | -10/+74 |
| | | | | | | | | | | | | Now simulated 'Memory' isn't just a single flat array. Instead it knows about segments and VMAs. The code segment will always be first, and the data/heap segment will always be second. The brk() syscall knows about the data segment. One nice side-effect is that I no longer need to mess with Memory initialization regardless of where I place my segments. | ||||
| * | 4612 | Kartik Agaram | 2018-09-29 | 1 | -11/+16 |
| | | |||||
| * | 4611 | Kartik Agaram | 2018-09-29 | 1 | -3/+4 |
| | | |||||
| * | 4520 - several syscalls for files | Kartik Agaram | 2018-08-13 | 1 | -0/+3 |
| | | |||||
| * | 4498 | Kartik Agaram | 2018-08-09 | 1 | -0/+18 |
| | | |||||
| * | 4482 | Kartik Agaram | 2018-08-04 | 1 | -0/+242 |