about summary refs log tree commit diff stats
path: root/subx/031check_operands.cc
Commit message (Collapse)AuthorAgeFilesLines
* switch to new syntax for segment headers in C++Kartik Agaram2019-05-181-19/+19
|
* start using the new carry flagKartik Agaram2019-05-131-0/+4
| | | | | Skimping on tests; the code changes seem pretty trivial. Will this fix CI?!
* 5114 - helper for idiv instructionKartik Agaram2019-04-211-0/+2
|
* 5001 - drop the :(scenario) DSLKartik Agaram2019-03-121-111/+189
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-1/+1
| | | | | | | | | | | | | | | | | | 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.
* 4941Kartik Agaram2019-01-211-4/+17
|
* 4940Kartik Agaram2019-01-211-4/+4
|
* 4909Kartik Agaram2019-01-051-17/+30
| | | | Improve error checking to warn on unexpected displacements as well.
* 4908Kartik Agaram2019-01-051-0/+1
| | | | | | | | Fix CI. a) Update canonical binaries. b) Fix an out-of-bounds access in `clear-stream`. This also required supporting a new instruction in `subx run` to load an imm8 into rm8.
* 4886Kartik Agaram2018-12-281-6/+2
|
* 4882Kartik Agaram2018-12-281-15/+26
|
* 4830Kartik Agaram2018-12-031-3/+9
| | | | | | New helper: printing a byte in textual (hex) form. This required adding instructions for bitwise shift operations.
* 4776Kartik Agaram2018-11-251-15/+11
| | | | | | | | | | | | | Crenshaw compiler now runs natively as well. It turns out I was misreading the Intel manual, and the jump instructions that I thought take disp16 operands actually take disp32 operands by default on both i686 and x86_64 processors. The disp16 versions are some holdover from the 16-bit days. This was the first time I've used one of these erstwhile-disp16 instructions, but I still haven't tested most of them. We'll see if we run into future issues.
* 4718Kartik Agaram2018-10-241-1/+1
|
* 4714Kartik Agaram2018-10-231-1/+21
| | | | Improve error-checking for unnecessary displacement operands.
* 4697Kartik Agaram2018-10-141-6/+16
|
* 4695Kartik Agaram2018-10-141-7/+7
|
* 4694Kartik Agaram2018-10-131-7/+7
| | | | Check for duplicate docstrings.
* 4668Kartik Agaram2018-10-051-4/+1
|
* 4503Kartik Agaram2018-09-221-0/+2
| | | | Include LEA (load effective address) in the SubX subset of x86 ISA.
* 4578 - subx: implement inc/dec operationsKartik Agaram2018-09-211-0/+18
|
* 4544Kartik Agaram2018-09-121-12/+12
| | | | | | | | 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.
* 4537Kartik Agaram2018-09-071-2/+1
| | | | | | | | | | | | | | | Streamline the factorial function; we don't need to save a stack variable into a register before operating on it. All instructions can take a stack variable directly. In the process we found two bugs: a) Opcode f7 was not implemented correctly. It was internally consistent but I'd never validated it against a natively running program. Turns out it encodes multiple instructions, not just 'not'. b) The way we look up imm32 operands was sometimes reading them before disp8/disp32 operands.
* 4527 - reading commandline argumentsKartik Agaram2018-08-301-0/+2
| | | | | | | | | | | The new example ex9 doesn't yet work natively. In the process I've emulated the kernel's role in providing args, implemented a couple of instructions acting on 8-bit operands (useful for ASCII string operations), and begun the start of the standard library (ascii_length is the same as strlen). At the level of SubX we're just only going to support ASCII.
* 4503Kartik Agaram2018-08-111-0/+9
|
* 4501Kartik Agaram2018-08-111-1/+1
|
* 4499Kartik Agaram2018-08-091-1/+1
| | | | | More tweaks for check passes. Ensure they're never first-class transforms.
* 4483Kartik Agaram2018-08-041-0/+511
Reorganize layers in accordance with the plan in layer 29.