about summary refs log tree commit diff stats
path: root/subx
Commit message (Collapse)AuthorAgeFilesLines
* 5188Kartik Agaram2019-05-182-12/+9
| | | | Clean up some unused constants.
* 5187Kartik Agaram2019-05-183-2/+3
| | | | CI should have been failing for a few days. Now fixed.
* switch to new syntax for segment headers in C++Kartik Agaram2019-05-1836-514/+481
|
* support the new segment syntax in assort.subxKartik Agaram2019-05-172-51/+35
| | | | | | | | | | | Now all implemented phases of the SubX translator in SubX support the new syntax: ✓ hex.subx (no changes required) survey.subx (not yet started) ✓ pack.subx (fixed here) ✓ assort.subx ✓ dquotes.subx (has failing tests for other reasons)
* another phase that supports the new segment syntaxKartik Agaram2019-05-172-18/+18
| | | | | | | | | | Current state: ✓ hex.subx (no changes required) survey.subx ✓ pack.subx (fixed here) assort.subx ✓ dquotes.subx (has failing tests for other reasons)
* start of new syntax for segment headersKartik Agaram2019-05-172-26/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Right now SubX defines headers with the following syntax: ``` === ... ``` The `...` can be either a numeric address or a name. Numeric addresses are useful for tests where we want to check addresses of individual instructions. Names are useful in real programs where we want to add to a segment in many places. This approach has long seemed a mess. It's hard to explain, and there's a certain amount of historical evolution that led to it that should be irrelevant to comprehend the current state of the codebase. I started out assuming the first segment was always code, before adding the special names 'code' and 'data'. We pretend to support more than two segments but we don't really. To simplify the code and explanation we'll move to a new syntax: ``` === <name> <address> ``` Code will always belong in the special name 'code', but it no longer has to be first. We need to migrate both our SubX-in-SubX phases and the C++ version. The plan is to start from the top down and update bootstrapping phases that've already been built (see commit 5102 for the list of phases). This commit updates pack.subx. Current state: ✓ hex.subx (no changes required) survey.subx ✓ pack.subx (fixed here) assort.subx dquotes.subx
* 5181Kartik Agaram2019-05-172-0/+20
| | | | Test for the bugfix of commit 2f49a27504.
* 5180Kartik Agaram2019-05-1611-44/+25
| | | | | | | Clean up some old TODOs related to our pre-mmap limitations. Also caught another case of using the wrong comparison. When comparing addresses, one must always use unsigned rather than signed jump instructions.
* 5179Kartik Agaram2019-05-161-4/+8
|
* complete the skeleton of dquotes.subxKartik Agaram2019-05-1512-49/+210
| | | | | | | | | | | | | | | | Still some failing tests: - emit-string-literal-data doesn't ignore metadata when computing the length of literal strings - emit-string-literal-data doesn't handle escape sequences One issue doesn't have a failing test: - emit-metadata doesn't handle string literals containing '/' All these open issues involve a common design question: how to parse a 'word' that includes a string literal that may include spaces. For everything else I know words can't contain spaces and datums can't contain slashes. But for string literals things are tougher.
* Merge branch 'dquotes' into dquotes-1Kartik Agaram2019-05-153-69/+132
|\
| * Merge branch 'master' into dquotesKartik Agaram2019-05-153-69/+132
| |\
| | * 5163Kartik Agaram2019-05-152-11/+27
| | | | | | | | | | | | A few more places with flag corrections.
| | * 5162Kartik Agaram2019-05-151-7/+7
| | |
| | * 5161Kartik Agaram2019-05-151-27/+27
| | |
| | * 5160Kartik Agaram2019-05-153-16/+6
| | |
| | * 5159Kartik Agaram2019-05-151-11/+68
| | | | | | | | | | | | One more instruction where I forgot to update the carry flag.
* | | .Kartik Agaram2019-05-142-9/+9
| | |
* | | fix a stale register value in dquotes.subxKartik Agaram2019-05-142-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | How did things seem to be working until now? - We were saving an address from the stack to stream.read - When we read this address in skip-chars-matching:loop, we used to stop early But now we've moved the stack to a larger address, one where the most significant byte is set. When the stack address now gets to skip-chars-matching:loop, it's treated as a negative number and we proceed through the loop. At which point we try to index into the array using it. No real test to be written to protect against this :(
* | | Merge branch 'dquotes' into dquotes-1Kartik Agaram2019-05-1328-264/+1499
|\| | | | | | | | | | | | | | dquotes.subx is now segfaulting after this merge. Seems to be trying to use addresses from the old stack.
| * | Merge branch 'master' into dquotesKartik Agaram2019-05-1327-357/+1363
| |\|
| | * 5158Kartik Agaram2019-05-131-3/+3
| | |
| | * start using the new carry flagKartik Agaram2019-05-1318-60/+96
| | | | | | | | | | | | | | | Skimping on tests; the code changes seem pretty trivial. Will this fix CI?!
| | * flag tests for opcode 3dKartik Agaram2019-05-131-4/+47
| | |
| | * .Kartik Agaram2019-05-131-5/+5
| | |
| | * .Kartik Agaram2019-05-131-3/+2
| | |
| | * .Kartik Agaram2019-05-133-13/+13
| | |
| | * flag tests for opcode 2dKartik Agaram2019-05-131-1/+46
| | |
| | * flag tests for opcode 81Kartik Agaram2019-05-131-17/+135
| | |
| | * flag tests for opcode 05Kartik Agaram2019-05-132-2/+51
| | |
| | * .Kartik Agaram2019-05-131-7/+8
| | |
| | * flag tests for opcode 3bKartik Agaram2019-05-131-3/+61
| | |
| | * .Kartik Agaram2019-05-133-54/+52
| | | | | | | | | | | | | | | | | | Standardize layout of some code fragments, and fix several bugs in computing the overflow flag in the process. a64 = b32 + c32 doesn't benefit from `a` being 64-bit without casting `b`.
| | * flag tests for opcode 2bKartik Agaram2019-05-131-7/+69
| | |
| | * .Kartik Agaram2019-05-131-8/+8
| | |
| | * flag tests for opcode 03Kartik Agaram2019-05-131-7/+69
| | |
| | * .Kartik Agaram2019-05-132-24/+46
| | | | | | | | | | | | | | | Make the first instruction described something that doesn't touch flags, so we don't introduce too much complexity all at once.
| | * carry flag thoroughly tested in layer 13Kartik Agaram2019-05-132-31/+131
| | | | | | | | | | | | | | | This is time-consuming mostly for me to come up with example scenarios testing all the different combinations of flags.
| | * .Kartik Agaram2019-05-132-20/+20
| | | | | | | | | | | | Correct some confusing log messages.
| | * CF needs special handling for some arithmetic opsKartik Agaram2019-05-125-86/+248
| | | | | | | | | | | | Inline some macro definitions.
| | * .Kartik Agaram2019-05-122-7/+0
| | | | | | | | | | | | Drop some prints as a first step to straightening things out.
| | * snapshot of carry flag implementationKartik Agaram2019-05-125-62/+147
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Tests failing. This approach seems wrong. I'm not sure even the tests are correct. Also, some open questions: 1. Should setting the overflow flag always set the carry flag? 2. Should the carry flag only be set on add/subtract/compare, or by all arithmetic ops? 3. Had to turn off the -ftrapv flag in `build`. Is there a way to detect overflow without actually causing overflow? Once we start setting CF correctly we have to implement jump above/below instructions (8- and 32-bit displacement variants). https://github.com/akkartik/mu/issues/30
| | * 5157Kartik Agaram2019-05-112-10/+10
| | | | | | | | | | | | | | | Support allocating more than 0x01000000 bytes (8MB) to a segment in the VM.
| | * 5156 - error-checking on writes to fileKartik Agaram2019-05-119-0/+29
| | | | | | | | | | | | | | | | | | | | | Pretty blunt for now; just abort the entire program on any failure to write. I'm encountering it because I'm somehow treating a stream address as a file descriptor. Maybe mmap is returning addresses below 0x08000000?
| | * 5155 - check for overflow in mmap segmentsKartik Agaram2019-05-112-1/+12
| | |
| | * 5154Kartik Agaram2019-05-118-0/+2
| | | | | | | | | | | | | | | Bugfix: I'd neglected to update the input stream's state when natively writing a stream to file.
| | * 5153Kartik Agaram2019-05-119-95/+215
| | |
| | * 5152 - check for stack underflow/overflow in VMKartik Agaram2019-05-116-22/+33
| | |
| * | Merge branch 'master' into dquotesKartik Agaram2019-05-1022-146/+277
| |\| | | | | | | | | | apps/dquotes still segfaulting on native run.
| * | implemented emit-metadatanc2019-05-041-1/+57
| | |
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-03 16:27:52 +0000