| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 4883 - rudimentary memory allocator | Kartik Agaram | 2018-12-28 | 1 | -7/+0 |
| | | |||||
| * | 4769 | Kartik Agaram | 2018-11-24 | 1 | -9/+37 |
| | | |||||
| * | 4668 | Kartik Agaram | 2018-10-05 | 1 | -1/+1 |
| | | |||||
| * | 4614 - redo simulated RAM | Kartik Agaram | 2018-09-29 | 1 | -2/+1 |
| | | | | | | | | | | | | 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. | ||||
| * | 4502 - support string literals directly in code | Kartik Agaram | 2018-09-22 | 1 | -0/+215 |
| Doesn't de-duplicate in the data segment, though. If you use the literal "foo" a hundred times in your code segment you're gonna spend a hundred times the space you need to. We can now simplify our test harness a bit in the factorial app, but we still have to put in commandline args to compare with manually. We only support length-prefixed strings, not null-terminated ones. | |||||