about summary refs log tree commit diff stats
path: root/subx/035labels.cc
Commit message (Collapse)AuthorAgeFilesLines
* 4874Kartik Agaram2018-12-251-0/+12
|
* 4773 - done with crenshaw chapter 2-1Kartik Agaram2018-11-241-1/+1
| | | | In the process I had to fix a couple more bugs in support for disp16 instructions.
* 4771Kartik Agaram2018-11-241-0/+5
| | | | | | | I stopped handling disp16 at some point, and using instructions with such an operand messes up segment alignment when generating ELF binaries. I don't test my ELF generation. This is a sign that maybe I should start.
* 4754 - allow data segment to refer to variablesKartik Agaram2018-11-191-3/+3
|
* 4678Kartik Agaram2018-10-101-2/+11
| | | | | | | | | A debugging aid: 'subx --map translate' dumps a mapping from functions to addresses to a file called "map", and 'subx --map run' loads the mapping in "map", augmenting debug traces. Let's see how much this helps. Debugging machine code has been pretty painful lately.
* 4668Kartik Agaram2018-10-051-28/+13
|
* 4661Kartik Agaram2018-10-041-3/+3
| | | | | Make segment management a little more consistent between initial segments and add-on segments (using `mmap`).
* 4640 - clear error message on missing libraryKartik Agaram2018-10-011-0/+3
|
* 4619 - new syscall: mmap()Kartik Agaram2018-09-291-1/+1
|
* 4616 - fix subx/examples/ex7Kartik Agaram2018-09-291-1/+30
| | | | | | | | | It was broken since I added support for global variables, back on Sep 1. One other subtle thing I've improved is the name `looks_like_hex_int`. We can now distinguish in the pack-operands transform between ignoring 'foo' because it doesn't look like a number, and immediately flagging '0xfoo' as an error because it *should* be a number.
* 4614 - redo simulated RAMKartik Agaram2018-09-291-1/+0
| | | | | | | | | | | 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.
* 4505Kartik Agaram2018-09-231-0/+10
| | | | | | | | | | | | Extract a helper from the factorial unit test: check_ints_equal. Start of a vocabulary for unit tests. I *could* also start thinking of supporting multi-file programs, but I'm going to resist the temptation for now. Copy helpers as necessary, and allow them to mutate and diverge for a while before we pummel them into a Procrustean "standard library". Extracting a body of shared code immediately starts to discourage innovation in the shared code.
* 4566Kartik Agaram2018-09-211-2/+2
| | | | | Neither jump nor call instructions support immediates. Drop that. The only form of absolute addressing relies on rm32.
* 4550Kartik Agaram2018-09-201-0/+17
|
* 4544Kartik Agaram2018-09-121-4/+4
| | | | | | | | Attempt #3 at fixing CI. In the process the feature gets a lot less half-baked. Ridiculously misleading that we had `has_metadata()` was special-cased to one specific transform. I suck.
* 4535 - support for global variable namesKartik Agaram2018-09-011-32/+18
|
* 4531 - automatically compute segment addressesKartik Agaram2018-09-011-10/+0
|
* 4523 - Give up on pass-through phasesKartik Agaram2018-08-201-0/+4
| | | | | | | | | | | | | | | | | | | | I'm going to continue using them for now, but I'm fairly certain now that they're just a temporary device to help rapidly-prototype ideas. The reason: there's just too many ways to abuse low-level features, and it ends up taking too much code to disallow things soon after you allow them. New plan: stop trying to write checks, just treat them as temporary conventions for now. Goal is now to just get the core sequence of passes nailed down. Then we'll start reimplementing them from the ground up. First implication of this new plan: ripping out most existing checks. I'm still going to eventually build type checks. But no degenerate checks for code just being too low-level. (This decision is the outcome of a few days of noodling over Forth and https://mastodon.social/@akkartik/100549913519614800.)
* 4517Kartik Agaram2018-08-131-2/+2
| | | | | We want to always print numbers in hex. This should make that a little more comprehensive.
* 4513 - disallow jumps across functionsKartik Agaram2018-08-121-2/+2
|
* 4512 - divide labels into two categoriesKartik Agaram2018-08-121-10/+9
| | | | | | | | | Targets you can jump to and ones you can call are conceptually disjoint sets. I'm highlighting these in Vim, but it's a pretty complex pattern. Arguably errors shouldn't be highlighted. Only warnings that are easy to be accidentally deployed.
* 4507Kartik Agaram2018-08-121-12/+32
| | | | | Side effect: better error messages when the tangler does something unexpected.
* 4505 - start warning on jumps without labelsKartik Agaram2018-08-111-0/+10
| | | | | As we climb the ladder of abstraction we'll gradually pull the ladder up behind ourselves.
* 4497Kartik Agaram2018-08-081-0/+14
|
* 4496Kartik Agaram2018-08-081-0/+16
|
* 4493Kartik Agaram2018-08-081-1/+19
|
* 4481Kartik Agaram2018-08-041-1/+1
|
* 4480Kartik Agaram2018-08-041-0/+161