about summary refs log tree commit diff stats
path: root/subx/035labels.cc
Commit message (Collapse)AuthorAgeFilesLines
* 5110Kartik Agaram2019-04-181-2/+3
|
* Add functionality to support labels as imm32 arguments to opcodesnc2019-04-181-0/+13
|
* 5008Kartik Agaram2019-03-171-4/+4
|
* 5001 - drop the :(scenario) DSLKartik Agaram2019-03-121-88/+142
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I've been saying for a while[1][2][3] that adding extra abstractions makes things harder for newcomers, and adding new notations doubly so. And then I notice this DSL in my own backyard. Makes me feel like a hypocrite. [1] https://news.ycombinator.com/item?id=13565743#13570092 [2] https://lobste.rs/s/to8wpr/configuration_files_are_canary_warning [3] https://lobste.rs/s/mdmcdi/little_languages_by_jon_bentley_1986#c_3miuf2 The implementation of the DSL was also highly hacky: a) It was happening in the tangle/ tool, but was utterly unrelated to tangling layers. b) There were several persnickety constraints on the different kinds of lines and the specific order they were expected in. I kept finding bugs where the translator would silently do the wrong thing. Or the error messages sucked, and readers may be stuck looking at the generated code to figure out what happened. Fixing error messages would require a lot more code, which is one of my arguments against DSLs in the first place: they may be easy to implement, but they're hard to design to go with the grain of the underlying platform. They require lots of iteration. Is that effort worth prioritizing in this project? On the other hand, the DSL did make at least some readers' life easier, the ones who weren't immediately put off by having to learn a strange syntax. There were fewer quotes to parse, fewer backslash escapes. Anyway, since there are also people who dislike having to put up with strange syntaxes, we'll call that consideration a wash and tear this DSL out. --- This commit was sheer drudgery. Hopefully it won't need to be redone with a new DSL because I grow sick of backslashes.
* 4987 - support `browse_trace` tool in SubXKartik Agaram2019-02-251-3/+3
| | | | | | | | | | | | | | | | | | I've extracted it into a separate binary, independent of my Mu prototype. I also cleaned up my tracing layer to be a little nicer. Major improvements: - Realized that incremental tracing really ought to be the default. And to minimize printing traces to screen. - Finally figured out how to combine layers and call stack frames in a single dimension of depth. The answer: optimize for the experience of `browse_trace`. Instructions occupy a range of depths based on their call stack frame, and minor details of an instruction lie one level deeper in each case. Other than that, I spent some time adjusting levels everywhere to make `browse_trace` useful.
* 4981 - no, go back to 3 phasesKartik Agaram2019-02-181-1/+22
| | | | | | | | | | | | | Considering how much trouble a merge phase would be (commit 4978), it seems simpler to just add the extra syntax for controlling the entry point of the generated ELF binary. But I wouldn't have noticed this if I hadn't taken the time to write out the commit messages of 4976 and 4978. Even if we happened to already have linked list primitives built, this may still be a good idea considering that I'm saving quite a lot of code in duplicated entrypoints.
* 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