about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 5995Kartik Agaram2020-02-081-7408/+7804
|
* 5994Kartik Agaram2020-02-081-3/+3
|
* 5993 - support for unlabeled loop instructionsKartik Agaram2020-02-082-3/+213
| | | | | Now that we have the infrastructure for emitting cleanup blocks, the labeled variants should be easy as well.
* 5992Kartik Agaram2020-02-072-12/+43
|
* 5991Kartik Agaram2020-02-072-1/+4
|
* 5990Kartik Agaram2020-02-061-1/+1
|
* 5989Kartik Agaram2020-02-062-17/+28
| | | | | | Start pushing dummy vars for labels on the stack as we encounter them. This won't affect cleanup code, but will make it easy to ensure that jumps are well-structured.
* 5988Kartik Agaram2020-02-062-41/+17
| | | | | | | Clean up data structures and eliminate the notion of named blocks. Named blocks still exist in the Mu language. But they get parsed into a uniform block data structure, same as unamed blocks.
* 5987Kartik Agaram2020-02-062-7/+7
|
* 5986Kartik Agaram2020-02-062-43/+1
|
* 5985Kartik Agaram2020-02-062-40/+30
| | | | | Standardize on a single block name. This simplifies some code and will also help in the next couple of steps.
* 5984 - start labeling all blocksKartik Agaram2020-02-052-165/+289
| | | | | | | | This will come in handy for the remaining cases where we need to clean up locals on the stack: loop after var non-local break with vars in intervening blocks non-local loop with vars in intervening blocks
* 5983 - fix an emulator bounds-check bugKartik Agaram2020-02-055-7/+7
| | | | | | It was possible for an instruction to write out of bounds of the memory data structure. Most of the time this worked fine. However if the block ever got resized and moved the out-of-bounds bytes no longer went along.
* 5982 - start putting block labels on the var stackKartik Agaram2020-02-052-26/+41
| | | | | | | | | | | | | | | | | | | | | Before: we detected labels using a '$' at the start of an arg, and turned them into literals. After: we put labels on the var stack and let the regular lookup of the var stack handle labels. This adds complexity in one place and removes it from another. The crucial benefit is that it allows us to store a block depth for each label. That will come in handy later. All this works only because of a salubrious coincidence: Mu labels are always at the start of a block, and jumps always refer to the name at the start of a block, even when the jump is in the forwards direction. So we never see label uses before definitions. Note on CI: this currently only works natively, not emulated.
* 5981 - decompose block cleanup into two traversalsKartik Agaram2020-02-022-35/+113
| | | | | Momentarily less efficient, but we will soon need the ability to emit cleanup code without losing all our state.
* 5980Kartik Agaram2020-02-021-3/+3
|
* 5979Kartik Agaram2020-02-021-2/+3
| | | | | | | Continuing to think about how to translate vars in a block when they're followed by early exits. To clean up everything between a statement and a target label, we need to know somehow the depth the target is defined at.
* 5978Kartik Agaram2020-02-021-1/+4
|
* 5977Kartik Agaram2020-02-022-4/+5
|
* 5976Kartik Agaram2020-02-021-3/+3
|
* 5975Kartik Agaram2020-02-021-7427/+7137
|
* 5974 - support for simple early exitsKartik Agaram2020-02-022-1/+84
| | | | | | | | | | | | | | | So far we only handle unlabeled break instructions correctly. That part is elegance itself. But the rest will need more work: a) For labeled breaks we need to insert code to unwind all intervening blocks. b) For unlabeled loops we need to insert code to unwind the current block and then loop. c) For labeled loops we need to insert code to unwind all intervening blocks and then loop. Is this even worth doing? I think so. It's pretty common for a conditional block inside a loop to 'continue'. That requires looping to somewhere non-local.
* 5973Kartik Agaram2020-02-021-369/+1
|
* 5972Kartik Agaram2020-02-011-6480/+6703
|
* 5971 - emit code with indentationKartik Agaram2020-02-012-256/+309
| | | | This is easy now that we're tracking block depths everywhere.
* 5970 - support block-scoped variablesKartik Agaram2020-02-012-6/+186
|
* 5969Kartik Agaram2020-02-011-27/+26
|
* 5968Kartik Agaram2020-02-014-33/+225
|
* 5967Kartik Agaram2020-02-011-0/+6
|
* 5966 - document all supported Mu instructionsKartik Agaram2020-01-317-22/+209
|
* 5965Kartik Agaram2020-01-312-10/+1
|
* 5964Kartik Agaram2020-01-301-3/+3
|
* 5963Kartik Agaram2020-01-301-3956/+3992
|
* 5962 - string literalsKartik Agaram2020-01-302-6/+43
|
* 5961Kartik Agaram2020-01-302-3/+2
|
* 5960Kartik Agaram2020-01-301-0/+1
|
* 5959Kartik Agaram2020-01-301-1/+1
|
* 5958Kartik Agaram2020-01-304-2848/+2871
|
* 5957 - bootstrap: stale checks for 2-byte opcodesKartik Agaram2020-01-301-2/+14
|
* 5956Kartik Agaram2020-01-291-27/+9
|
* 5955 - error messages when translating Mu programsKartik Agaram2020-01-291-1/+1
|
* 5954 - 'factorial' working!Kartik Agaram2020-01-292-0/+98
|
* 5953 - 'multiply' instructionKartik Agaram2020-01-292-0/+13
|
* 5952Kartik Agaram2020-01-291-2231/+2573
|
* 5951 - 'compare' instructionsKartik Agaram2020-01-292-9/+376
|
* 5950Kartik Agaram2020-01-292-0/+189
|
* 5949Kartik Agaram2020-01-294-6505/+7312
|
* 5948 - branching to named blocksKartik Agaram2020-01-2916-32/+476
|
* 5947 - add a new field to primitivesKartik Agaram2020-01-292-4/+92
| | | | For supporting branches with a target.
* 5946Kartik Agaram2020-01-292-6/+6
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-20 06:22:40 +0000