about summary refs log tree commit diff stats
path: root/apps/mu.subx
Commit message (Collapse)AuthorAgeFilesLines
* -Kartik Agaram2020-05-181-60/+77
| | | | | | | | Trying to switch gears a bit and scope out how much is left. Code-generation should be a lot less work since few signatures need to change. Hopefully getting to 55% down mu.subx will really be 90% of the way. In particular, there are 17 signature changes remaining that need to patch their calling functions as well.
* -Kartik Agaram2020-05-181-1/+1
|
* mu.subx: mu-block-nameKartik Agaram2020-05-181-29/+32
|
* mu.subx: append-to-blockKartik Agaram2020-05-181-3/+6
| | | | | | | | I'm just cleaning up the final call to append-list, and it's internally consistent if `block` can be an `addr`. I don't know yet if that makes sense for callers. I think I also found a bug in append-to-block: it was clobbering eax.
* mu.subx: append-listKartik Agaram2020-05-181-30/+52
| | | | | populate-function-header _almost_ done. I think we just need to fix `push` next.
* mu.subx: parse-var-with-typeKartik Agaram2020-05-181-7/+2
|
* mu.subx: parse-type-treeKartik Agaram2020-05-181-20/+31
|
* mu.subx: parse-typeKartik Agaram2020-05-181-30/+21
|
* mu.subx: add-operation-and-inputs-to-stmtKartik Agaram2020-05-181-2/+2
|
* mu.subx: pos-slice, pos-or-insert-sliceKartik Agaram2020-05-181-4/+13
|
* mu.subx: some calls to slice-to-stringKartik Agaram2020-05-181-5/+5
|
* -Kartik Agaram2020-05-181-21/+21
|
* mu.subx: partial parse-var-with-typeKartik Agaram2020-05-181-6/+11
|
* mu.subx: new-var, new-var-from-sliceKartik Agaram2020-05-181-33/+55
|
* mu.subx: size of 'vars' stackKartik Agaram2020-05-181-27/+27
|
* mu.subx: parse-muKartik Agaram2020-05-181-3/+14
|
* -Kartik Agaram2020-05-181-21/+9
|
* -Kartik Agaram2020-05-181-29/+28
|
* mu.subx: new-var, typeinfo entriesKartik Agaram2020-05-181-29/+76
|
* -Kartik Agaram2020-05-181-3/+3
|
* -Kartik Agaram2020-05-181-7/+9
|
* mu.subx: find-or-create-typeinfoKartik Agaram2020-05-181-29/+65
|
* mu.subx: offsets for type data structuresKartik Agaram2020-05-181-8/+8
|
* -Kartik Agaram2020-05-181-6/+0
|
* mu.subx: uses of Program->functionsKartik Agaram2020-05-181-11/+29
| | | | | This is all very superficial. I'm not going to be able to run tests for a long time.
* starting to fix mu.subxKartik Agaram2020-05-181-37/+42
| | | | | Update offset declarations in function data structures for starters. We still need to go over the entire file to actually use them.
* -Kartik Agaram2020-05-181-6/+6
|
* table primitives workingKartik Agaram2020-05-181-0/+1
| | | | $ ./translate_subx init.linux 0*.subx && ./a.elf test
* 6219Kartik Agaram2020-05-181-0/+3
|
* 6216Kartik Agaram2020-05-051-12/+7
|
* 6209Kartik Agaram2020-04-241-1/+2
|
* 6208Kartik Agaram2020-04-221-16/+2
|
* 6205Kartik Agaram2020-04-151-156/+31
| | | | Rip out scaffolding for function overloading.
* 6204Kartik Agaram2020-04-151-28/+0
|
* 6203Kartik Agaram2020-04-121-115/+162
|
* 6182 - start of support for safe handlesKartik Agaram2020-04-031-20/+20
| | | | | | | | | | | | | | 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.
* 6181Kartik Agaram2020-04-031-1/+1
|
* 6158 - standardize opcode namesKartik Agaram2020-03-211-68/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* 6152 - fix regression in factorial.muKartik Agaram2020-03-151-2/+100
| | | | | I had to amend commit 6148 three times yesterday as I kept finding bugs by inspection. And yet I stubbornly thought I didn't need a test.
* 6150 - call-by-reference is workingKartik Agaram2020-03-141-0/+79
|
* 6149 - pass multi-word objects to functionsKartik Agaram2020-03-141-4/+103
| | | | This is quite inefficient; don't use it for very large objects.
* 6148Kartik Agaram2020-03-141-2/+42
|
* 6147Kartik Agaram2020-03-141-10/+10
|
* 6145 - 'address' operatorKartik Agaram2020-03-141-0/+74
| | | | | This could be a can of worms, but I think I have a set of checks that will keep use of addresses type-safe.
* 6133Kartik Agaram2020-03-121-3/+65
|
* 6132Kartik Agaram2020-03-121-30/+30
|
* 6131 - operating on arrays on the stackKartik Agaram2020-03-121-45/+299
|
* 6128 - arrays on the stackKartik Agaram2020-03-111-10/+145
|
* 6126 - support 8-byte register namesKartik Agaram2020-03-111-3/+3
| | | | Using these is quite unsafe. But what isn't, here?
* 6125Kartik Agaram2020-03-111-6/+15
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-25 17:27:57 +0000