Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | 889 - ah, fixed that final error | Kartik K. Agaram | 2015-03-12 | 1 | -0/+32 |
| | |||||
* | 888 | Kartik K. Agaram | 2015-03-12 | 1 | -20/+0 |
| | |||||
* | 887 - first pass of pagination bugs squashed | Kartik K. Agaram | 2015-03-11 | 1 | -0/+61 |
| | | | | | | | | This must be the second or third time I've mis-tagged a literal as 'integer'.. I also spotted an error with the cursor bouncing out above the screen area of the trace browser. But I haven't been able to recreate it.. | ||||
* | 886 | Kartik K. Agaram | 2015-03-11 | 1 | -0/+42 |
| | | | | Another test, but now the tests run 50% slower (8 vs 12 minutes) | ||||
* | 885 | Kartik K. Agaram | 2015-03-11 | 1 | -1/+1 |
| | |||||
* | 884 - expand/collapse now seems page-aware | Kartik K. Agaram | 2015-03-11 | 1 | -0/+112 |
| | |||||
* | 883 | Kartik K. Agaram | 2015-03-11 | 1 | -1/+1 |
| | |||||
* | 882 | Kartik K. Agaram | 2015-03-10 | 1 | -1/+31 |
| | |||||
* | 881 | Kartik K. Agaram | 2015-03-10 | 1 | -0/+1 |
| | |||||
* | 879 - debug prints shouldn't mess up interactive runs | Kartik K. Agaram | 2015-03-09 | 1 | -1/+1 |
| | |||||
* | 877 - supporting pages in expand | Kartik K. Agaram | 2015-03-09 | 1 | -1/+20 |
| | |||||
* | 875 | Kartik K. Agaram | 2015-03-09 | 1 | -0/+26 |
| | |||||
* | 874 | Kartik K. Agaram | 2015-03-09 | 1 | -3/+3 |
| | |||||
* | 872 | Kartik K. Agaram | 2015-03-09 | 1 | -1/+1 |
| | |||||
* | 871 | Kartik K. Agaram | 2015-03-08 | 1 | -8/+8 |
| | |||||
* | 870 - page-up starting to look solid | Kartik K. Agaram | 2015-03-08 | 1 | -0/+70 |
| | |||||
* | 869 | Kartik K. Agaram | 2015-03-07 | 1 | -0/+278 |
| | | | | | | | The repeated need for bugfixes after every new test isn't very confidence-inducing. On the other hand, I'm starting to get into a cadence where fixes have been easy to make. We'll see. Monotonic progress continues. | ||||
* | 868 | Kartik K. Agaram | 2015-03-07 | 1 | -8/+0 |
| | |||||
* | 867 | Kartik K. Agaram | 2015-03-06 | 1 | -0/+16 |
| | |||||
* | 866 - starting to finally gain confidence in page-up | Kartik K. Agaram | 2015-03-06 | 1 | -0/+64 |
| | |||||
* | 864 | Kartik K. Agaram | 2015-03-06 | 1 | -13/+26 |
| | |||||
* | 860 | Kartik K. Agaram | 2015-03-04 | 1 | -1/+28 |
| | | | | A new intermediate test might help. | ||||
* | 859 | Kartik K. Agaram | 2015-03-02 | 1 | -0/+163 |
| | | | | | | Intermediate snapshot after 2 days of desultorily debugging this still-failing test. Our divising of the problem into cases just seems wrong right now. | ||||
* | 856 - stop perturbing traces on new functions | Kartik K. Agaram | 2015-03-01 | 1 | -152/+131 |
| | | | | | Still hacky, but now we can standardize the couple of different workflows we need. | ||||
* | 855 - page-up fleshed out, but needs a lot more tests | Kartik K. Agaram | 2015-03-01 | 1 | -0/+14 |
| | |||||
* | 853 | Kartik K. Agaram | 2015-02-28 | 1 | -6/+19 |
| | |||||
* | 852 - page-down stitches expanded lines properly | Kartik K. Agaram | 2015-02-28 | 1 | -0/+35 |
| | |||||
* | 848 | Kartik K. Agaram | 2015-02-27 | 1 | -7/+6 |
| | |||||
* | 847 | Kartik K. Agaram | 2015-02-26 | 1 | -0/+14 |
| | |||||
* | 846 | Kartik K. Agaram | 2015-02-26 | 1 | -0/+13 |
| | |||||
* | 845 | Kartik K. Agaram | 2015-02-26 | 1 | -4/+15 |
| | |||||
* | 844 - start of support for page navigation | Kartik K. Agaram | 2015-02-26 | 1 | -0/+19 |
| | | | | | To keep things simple we won't allow line navigation to span pages. You have to switch pages with dedicated hotkeys. | ||||
* | 843 | Kartik K. Agaram | 2015-02-26 | 1 | -57/+57 |
| | |||||
* | 842 | Kartik K. Agaram | 2015-02-26 | 1 | -490/+487 |
| | |||||
* | 841 - no obvious optimization targets | Kartik K. Agaram | 2015-02-26 | 1 | -487/+490 |
| | | | | | | | | | | | | | | | | | 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. | ||||
* | 838 | Kartik K. Agaram | 2015-02-26 | 1 | -1/+15 |
| | |||||
* | 837 - pagination in the trace browser | Kartik K. Agaram | 2015-02-26 | 1 | -0/+81 |
| | | | | Still not finished; we're maybe halfway through the necessary tests. | ||||
* | 836 | Kartik K. Agaram | 2015-02-26 | 1 | -6/+6 |
| | |||||
* | 760 | Kartik K. Agaram | 2015-02-16 | 1 | -1/+1 |
| | | | | This speeds up the final test but not all together. | ||||
* | 759 - trace.arc.t 13% faster | Kartik K. Agaram | 2015-02-16 | 1 | -0/+1 |
| | | | | Something wrong with my profiling, though. Numbers aren't adding up. | ||||
* | 757 - collapse now kinda working | Kartik K. Agaram | 2015-02-16 | 1 | -0/+32 |
| | | | | | Tests are getting slow so quickly that I'm tempted to push forward the rewrite to C. | ||||
* | 756 - first scenario for collapse | Kartik K. Agaram | 2015-02-16 | 1 | -26/+51 |
| | |||||
* | 755 - cursor can only lie on top-level lines | Kartik K. Agaram | 2015-02-16 | 1 | -0/+86 |
| | | | | | | | | This allows the initial model of a trace to have just one new number: the currently expanded row. We'll make it more flexible later if we feel the need. Still no collapsing lines, though. But we're getting there. | ||||
* | 754 - traces are part of screen state | Kartik K. Agaram | 2015-02-16 | 1 | -7/+7 |
| | |||||
* | 749 - cleaner screen tests | Kartik K. Agaram | 2015-02-15 | 1 | -0/+55 |
| | |||||
* | 748 | Kartik K. Agaram | 2015-02-15 | 1 | -11/+11 |
| | |||||
* | 747 | Kartik K. Agaram | 2015-02-15 | 1 | -8/+0 |
| | | | | This bugfix is not tested yet, but that's in the works. | ||||
* | 746 - toggle a set of lines by hitting enter twice | Kartik K. Agaram | 2015-02-12 | 1 | -0/+21 |
| | | | | This just supports it, but we don't actually have collapse yet. | ||||
* | 745 - first test of expand functionality | Kartik K. Agaram | 2015-02-11 | 1 | -0/+72 |
| | | | | | | | | | | Expanding trace items, of course, doesn't work on anything but the last item. But we've now caught automatic tests up to the state of development. These tests are hugely expensive. Previous .t files run in ~30s. Already the trace browser tests clock in at 2 minutes. And we're just getting started. Time to explore reimplementing the mu VM in C. | ||||
* | 744 - test cursor movement in trace browser | Kartik K. Agaram | 2015-02-11 | 1 | -0/+149 |
| | | | | | | Don't prevent run-code from clobbering existing functions, but warn because it makes traces easier to read if the different sections of a test can be distinguished. |