| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | standard library tests all passing | Kartik Agaram | 2020-05-18 | 1 | -43/+64 |
| | | |||||
| * | 6184 | Kartik Agaram | 2020-04-05 | 1 | -1/+0 |
| | | | | | Why the heck are we bumping this pointer? Seems like a bug. | ||||
| * | 6182 - start of support for safe handles | Kartik Agaram | 2020-04-03 | 1 | -14/+14 |
| | | | | | | | | | | | | | | | So far it's unclear how to do this in a series of small commits. Still nibbling around the edges. In this commit we standardize some terminology: The length of an array or stream is denominated in the high-level elements. The _size_ is denominated in bytes. The thing we encode into the type is always the size, not the length. There's still an open question of what to do about the Mu `length` operator. I'd like to modify it to provide the length. Currently it provides the size. If I can't fix that I'll rename it. | ||||
| * | 6158 - standardize opcode names | Kartik Agaram | 2020-03-21 | 1 | -4/+4 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | At the lowest level, SubX without syntax sugar uses names without prepositions. For example, 01 and 03 are both called 'add', irrespective of source and destination operand. Horizontal space is at a premium, and we rely on the comments at the end of each line to fully describe what is happening. Above that, however, we standardize on a slightly different naming convention across: a) SubX with syntax sugar, b) Mu, and c) the SubX code that the Mu compiler emits. Conventions, in brief: - by default, the source is on the left and destination on the right. e.g. add %eax, 1/r32/ecx ("add eax to ecx") - prepositions reverse the direction. e.g. add-to %eax, 1/r32/ecx ("add ecx to eax") subtract-from %eax, 1/r32/ecx ("subtract ecx from eax") - by default, comparisons are left to right while 'compare<-' reverses. Before, I was sometimes swapping args to make the operation more obvious, but that would complicate the code-generation of the Mu compiler, and it's nice to be able to read the output of the compiler just like hand-written code. One place where SubX differs from Mu: copy opcodes are called '<-' and '->'. Hopefully that fits with the spirit of Mu rather than the letter of the 'copy' and 'copy-to' instructions. | ||||
| * | 6157 | Kartik Agaram | 2020-03-21 | 1 | -247/+41 |
| | | |||||
| * | 6083 | Kartik Agaram | 2020-03-06 | 1 | -4/+4 |
| | | |||||
| * | 5924 | Kartik Agaram | 2020-01-27 | 1 | -30/+30 |
| | | |||||
| * | 5897 - rename comparison instructions | Kartik Agaram | 2020-01-16 | 1 | -7/+7 |
| | | | | | | | | Signed and unsigned don't quite capture the essence of what the different combinations of x86 flags are doing for SubX. The crucial distinction is that one set of comparison operators is for integers and the second is for addresses. | ||||
| * | 5888 | Kartik Agaram | 2020-01-14 | 1 | -228/+222 |
| | | |||||
| * | 5887 - reorganize library | Kartik Agaram | 2020-01-14 | 1 | -0/+605 |
| Layers 0-89 are used in self-hosting SubX. Layers 90-99 are not needed for self-hosting SubX, and therefore could use transitional levels of syntax sugar. Layers 100 and up use all SubX syntax sugar. | |||||