about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 842Kartik K. Agaram2015-02-263-725/+578
|
* 841 - no obvious optimization targetsKartik K. Agaram2015-02-262-578/+584
| | | | | | | | | | | | | | | | | Top functions (ms and #calls): run-for-time-slice 209953 184 m 63880 99478 canonize 63568 307282 setm 44378 67281 sizeof 37786 130452 absolutize 36587 370943 addr 34567 146896 typeof 17395 63661 parse-instr 11670 99243 space 10988 561036 typeinfo 10691 563272 absolutize seems like a target.
* 840Kartik K. Agaram2015-02-261-93/+0
|
* 839 - profiling parse-traceKartik K. Agaram2015-02-261-0/+93
| | | | | | | | Ok, it's not super-linear, at least on the level of mu. Parsing is just inefficient. To profile stages inside main: grep "^run: " .traces/p? |column 2 |perl -pwe 's,.*/([^/]*)/([^/]*) ,$1/$2 ,' |sort |freq |sort -nrk2
* 838Kartik K. Agaram2015-02-261-1/+15
|
* 837 - pagination in the trace browserKartik K. Agaram2015-02-262-25/+123
| | | | Still not finished; we're maybe halfway through the necessary tests.
* 836Kartik K. Agaram2015-02-262-7/+9
|
* 835Kartik K. Agaram2015-02-261-14/+12
|
* 833Kartik K. Agaram2015-02-251-6/+4
|
* 832 - call-stack for C++ versionKartik K. Agaram2015-02-2554-173/+203
| | | | | | | | | | These #defines and references now span many different layers. Let's see if the lack of encapsulation causes problems. Also interesting to run into a case where I need to modify a foundational layer and touch every single scenario/trace. Only alternative was to duplicate all the different layers that add instructions. Sign of problems with this model?
* 831 - wire up trace browser to interactive replKartik K. Agaram2015-02-242-18/+68
|
* 830Kartik K. Agaram2015-02-241-9/+9
|
* 829 - warn if I forgot to freeze a functionKartik K. Agaram2015-02-241-4/+5
|
* 828 - interactive replKartik K. Agaram2015-02-232-16/+36
| | | | | Still klunky since mu has no notion of a return value. I find myself using $print all the time.
* 826 - augment name bindings when extending a functionKartik K. Agaram2015-02-231-3/+4
| | | | This becomes important as we get closer to a repl for mu.
* 825Kartik K. Agaram2015-02-221-0/+3
|
* 824Kartik K. Agaram2015-02-221-1/+1
|
* 823Kartik K. Agaram2015-02-223-0/+154
|
* 822Kartik K. Agaram2015-02-221-1/+0
|
* 821Kartik K. Agaram2015-02-221-6/+2
|
* 820 - bugfix in get-addressKartik K. Agaram2015-02-222-2/+8
|
* 819Kartik K. Agaram2015-02-223-8/+8
|
* 818Kartik K. Agaram2015-02-221-0/+1
|
* 817Kartik K. Agaram2015-02-223-0/+136
|
* 816Kartik K. Agaram2015-02-221-0/+3
|
* 815Kartik K. Agaram2015-02-223-10/+1
|
* 814Kartik K. Agaram2015-02-224-3/+67
|
* 813Kartik K. Agaram2015-02-224-33/+30
|
* 812Kartik K. Agaram2015-02-212-5/+0
|
* 811 - first test for arraysKartik K. Agaram2015-02-214-4/+95
|
* 810Kartik K. Agaram2015-02-213-6/+7
|
* 809Kartik K. Agaram2015-02-211-1/+2
|
* 808Kartik K. Agaram2015-02-212-0/+24
|
* 807 - first passing test for indirect addressingKartik K. Agaram2015-02-212-0/+104
|
* 806 - start parsing reagent metadataKartik K. Agaram2015-02-213-2/+27
|
* 805Kartik K. Agaram2015-02-201-0/+3
|
* 804 - reagent can have multiple typesKartik K. Agaram2015-02-208-42/+59
|
* 803Kartik K. Agaram2015-02-201-0/+0
|
* 802 - mu commentsKartik K. Agaram2015-02-203-8/+20
| | | | | | Comments at end of line are still hacky; we just rely on the fact that excess ingredients do no harm. We'll need to be smarter when we get our first vararg recipe.
* 801Kartik K. Agaram2015-02-202-0/+63
|
* 800Kartik K. Agaram2015-02-202-8/+7
|
* 799 - 'get' on recordsKartik K. Agaram2015-02-203-0/+83
|
* 798 - start of record supportKartik K. Agaram2015-02-194-8/+70
|
* 797 - comparison instructionsKartik K. Agaram2015-02-1913-0/+542
|
* 796 - jump instructions doneKartik K. Agaram2015-02-199-5/+170
|
* 795Kartik K. Agaram2015-02-193-0/+60
|
* 794 - first jump instructionKartik K. Agaram2015-02-191-0/+32
|
* 793Kartik K. Agaram2015-02-193-48/+46
|
* 792Kartik K. Agaram2015-02-191-0/+28
|
* 791Kartik K. Agaram2015-02-191-6/+6
|