about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 6205Kartik Agaram2020-04-152-156/+31
| | | | Rip out scaffolding for function overloading.
* 6204Kartik Agaram2020-04-152-28/+0
|
* 6203Kartik Agaram2020-04-122-115/+162
|
* 6202Kartik Agaram2020-04-111-1/+0
|
* 6201Kartik Agaram2020-04-092-6/+6
| | | | Fix CI. Amazing how misleading the ofstream API is when coercing to bool.
* 6200 - --dump is not needed for incremental tracesKartik Agaram2020-04-094-11/+7
| | | | | | | | This undoes commit 5764, which was ill-considered. We already had incremental prints at that point to 'last_run'. As long as we don't run out of RAM on large traces, there doesn't seem any need to print to stderr. Now '--dump' is only needed when juggling multiple traces.
* 6199Kartik Agaram2020-04-081-1/+1
|
* 6198Kartik Agaram2020-04-082-14/+10
|
* 6197Kartik Agaram2020-04-082-18/+18
|
* 6196Kartik Agaram2020-04-062-2/+2
|
* 6195Kartik Agaram2020-04-062-1/+1
| | | | This bug was never caught because we've never tested with more than 2 segments.
* 6194Kartik Agaram2020-04-062-3/+6
|
* 6193Kartik Agaram2020-04-062-3/+6
|
* 6192Kartik Agaram2020-04-062-3/+6
|
* 6191Kartik Agaram2020-04-062-5/+6
|
* 6190Kartik Agaram2020-04-061-31/+33
|
* 6189Kartik Agaram2020-04-062-15/+14
|
* 6188Kartik Agaram2020-04-061-7/+18
|
* 6187Kartik Agaram2020-04-062-1/+3
|
* 6186Kartik Agaram2020-04-062-6/+2
|
* 6185Kartik Agaram2020-04-061-8/+8
|
* 6184Kartik Agaram2020-04-052-1/+0
| | | | Why the heck are we bumping this pointer? Seems like a bug.
* 6183Kartik Agaram2020-04-031-1/+1
| | | | Bugfix in CI setup.
* 6182 - start of support for safe handlesKartik Agaram2020-04-0342-221/+221
| | | | | | | | | | | | | | 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-0318-51/+54
|
* 6180Kartik Agaram2020-04-032-73/+11
| | | | | It's going to be hard work retrofitting 8-byte handles in place of 4-byte addrs. Here we just clean up some unused args.
* 6179Kartik Agaram2020-04-031-2/+2
|
* 6178Kartik Agaram2020-03-318-8/+40
|
* 6177Kartik Agaram2020-03-291-4/+1
|
* 6176Kartik Agaram2020-03-291-6/+6
|
* 6175 - syntax highlighting for dteKartik Agaram2020-03-292-0/+72
| | | | https://gitlab.com/craigbarnes/dte
* 6174Kartik Agaram2020-03-271-1/+1
|
* 6173Kartik Agaram2020-03-272-10/+24
|
* 6172Kartik Agaram2020-03-261-1/+1
| | | | Typo in stats: use the same measures as in previous lines.
* 6171Kartik Agaram2020-03-251-2/+2
|
* 6170Kartik Agaram2020-03-252-6/+6
|
* 6169Kartik Agaram2020-03-252-2/+2
|
* 6168Kartik Agaram2020-03-251-1/+1
|
* 6167Kartik Agaram2020-03-251-1/+1
|
* 6166Kartik Agaram2020-03-251-2/+2
|
* 6165Kartik Agaram2020-03-251-10/+10
|
* 6164Kartik Agaram2020-03-242-93/+93
|
* 6163Kartik Agaram2020-03-231-0/+248
|
* 6162Kartik Agaram2020-03-237-36/+45
|
* 6161Kartik Agaram2020-03-221-2/+2
|
* 6160 - plan for safe heap accessKartik Agaram2020-03-212-2/+55
| | | | | | | | | Based on apps/handle.subx (commit 4894), but we're able to simplify it further now that we know more about the situation we find ourselves in. 6 instructions, zero pushes or pops. Before I can start building this, I need to reorganize my use of handles. They're going to be fat pointers so we can't store them in registers anymore.
* 6159Kartik Agaram2020-03-211-218/+165
|
* 6158 - standardize opcode namesKartik Agaram2020-03-215-107/+87
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* 6157Kartik Agaram2020-03-212-247/+41
|
* 6156Kartik Agaram2020-03-211-11/+0
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-26 14:08:06 +0000