Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | 4966 | Kartik Agaram | 2019-02-14 | 4 | -24/+23 |
| | | | | Standardize how we show register allocation decisions. | ||||
* | 4965 | Kartik Agaram | 2019-02-14 | 7 | -25/+31 |
| | |||||
* | 4964 | Kartik Agaram | 2019-02-14 | 2 | -3/+3 |
| | |||||
* | 4963 | Kartik Agaram | 2019-02-14 | 4 | -9/+9 |
| | |||||
* | 4962 | Kartik Agaram | 2019-02-14 | 1 | -38/+40 |
| | | | | | Build the C++ version optimized by default when building/running all apps. We have enough apps now that the cost of optimized builds is worthwhile. | ||||
* | 4961 | Kartik Agaram | 2019-02-14 | 31 | -209/+253 |
| | |||||
* | 4960 | Kartik Agaram | 2019-02-13 | 2 | -8/+6 |
| | | | | | I think I don't need to special-case packing for different segments. That should massively cut down on the number of tests. | ||||
* | 4959 | Kartik Agaram | 2019-02-13 | 2 | -12/+30 |
| | | | | | It's always seemed ugly to explain the rules for segment names. Let's just always require a fixed name for the code and data segments. | ||||
* | 4958 - all my apps fit in 4KB so far | Kartik Agaram | 2019-02-11 | 1 | -0/+16 |
| | | | | (excluding tests) | ||||
* | 4956 | Kartik Agaram | 2019-02-11 | 2 | -1/+69 |
| | |||||
* | 4955 | Kartik Agaram | 2019-02-10 | 8 | -20/+380 |
| | | | | Starting to build up Phase 2 (apps/pack) out of recently designed primitives. | ||||
* | 4954 | Kartik Agaram | 2019-02-10 | 9 | -39/+141 |
| | |||||
* | 4952 | Kartik Agaram | 2019-02-05 | 9 | -13/+474 |
| | |||||
* | 4951 | Kartik Agaram | 2019-02-03 | 16 | -78/+273 |
| | | | | Cleaner way to compare streams in tests. | ||||
* | 4950 | Kartik Agaram | 2019-02-03 | 15 | -0/+0 |
| | |||||
* | 4949 | Kartik Agaram | 2019-02-02 | 24 | -42/+62 |
| | |||||
* | 4948 | Kartik Agaram | 2019-02-02 | 2 | -6/+341 |
| | | | | | This seems like the final helper we need for Phase 2. Now to build the business logic itself. | ||||
* | 4947 | Kartik Agaram | 2019-02-01 | 2 | -0/+2 |
| | | | | | | | | Bugfix: has-metadata? was corrupting registers Seems uneconomic to write tests for stuff like this. Assembly is just not the right layer to try to come up with a general solution or process. Keep running your code and wait to find signs of breakage. | ||||
* | 4946 | Kartik Agaram | 2019-02-01 | 2 | -2/+66 |
| | |||||
* | 4945 | Kartik Agaram | 2019-02-01 | 7 | -0/+70 |
| | |||||
* | 4944 | Kartik Agaram | 2019-01-30 | 1 | -4/+4 |
| | | | | Improve syntax highlighting in the Readme. | ||||
* | 4943 | Kartik Agaram | 2019-01-30 | 2 | -3/+2 |
| | |||||
* | 4941 | Kartik Agaram | 2019-01-21 | 1 | -4/+17 |
| | |||||
* | 4940 | Kartik Agaram | 2019-01-21 | 1 | -4/+4 |
| | |||||
* | 4939 | Kartik Agaram | 2019-01-21 | 3 | -3/+253 |
| | |||||
* | 4938 | Kartik Agaram | 2019-01-20 | 7 | -44/+57 |
| | |||||
* | 4937 | Kartik Agaram | 2019-01-20 | 7 | -9/+432 |
| | |||||
* | 4936 | Kartik Agaram | 2019-01-18 | 1 | -1/+1 |
| | |||||
* | 4935 | Kartik Agaram | 2019-01-16 | 1 | -2/+2 |
| | |||||
* | 4934 | Kartik Agaram | 2019-01-16 | 4 | -6/+6 |
| | |||||
* | 4933 | Kartik Agaram | 2019-01-16 | 7 | -50/+50 |
| | |||||
* | 4931 | Kartik Agaram | 2019-01-16 | 1 | -1/+0 |
| | |||||
* | 4930 | Kartik Agaram | 2019-01-15 | 7 | -2/+231 |
| | |||||
* | 4929 | Kartik Agaram | 2019-01-15 | 15 | -57/+28 |
| | | | | Clean up primitives for converting from/to hex chars. | ||||
* | 4928 | Kartik Agaram | 2019-01-14 | 6 | -3/+53 |
| | |||||
* | 4927 | Kartik Agaram | 2019-01-14 | 7 | -12/+146 |
| | |||||
* | 4926 | Kartik Agaram | 2019-01-14 | 6 | -4/+70 |
| | |||||
* | 4925 | Kartik Agaram | 2019-01-14 | 8 | -29/+185 |
| | |||||
* | 4923 | Kartik Agaram | 2019-01-12 | 8 | -26/+27 |
| | | | | | We want slice-equal? for length-prefixed strings, not null-terminated "kernel" strings. | ||||
* | 4922 | Kartik Agaram | 2019-01-11 | 1 | -6/+6 |
| | |||||
* | 4921 | Kartik Agaram | 2019-01-11 | 1 | -2/+2 |
| | |||||
* | 4920 | Kartik Agaram | 2019-01-11 | 10 | -183/+467 |
| | |||||
* | 4918 | Kartik Agaram | 2019-01-10 | 4 | -4/+4 |
| | |||||
* | 4917 | Kartik Agaram | 2019-01-10 | 1 | -140/+0 |
| | |||||
* | 4916 | Kartik Agaram | 2019-01-10 | 12 | -24/+611 |
| | | | | | In the process of building slice primitives I found an out-of-bounds access in write-byte. | ||||
* | 4915 | Kartik Agaram | 2019-01-08 | 4 | -11/+213 |
| | | | | | | In the process of building next-token I finally added some support for a debugging situation I've found myself in a couple of times: wondering "what changed this memory location"? | ||||
* | 4913 | Kartik Agaram | 2019-01-07 | 7 | -2/+472 |
| | |||||
* | 4912 | Kartik Agaram | 2019-01-06 | 1 | -3/+117 |
| | |||||
* | 4911 | Kartik Agaram | 2019-01-06 | 11 | -21/+223 |
| | |||||
* | 4909 | Kartik Agaram | 2019-01-05 | 2 | -19/+32 |
| | | | | Improve error checking to warn on unexpected displacements as well. |