Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | 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 |
| | |||||
* | 4942 | Kartik Agaram | 2019-01-21 | 4 | -324/+337 |
| | |||||
* | 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 | 8 | -721/+729 |
| | |||||
* | 4937 | Kartik Agaram | 2019-01-20 | 8 | -452/+1282 |
| | |||||
* | 4936 | Kartik Agaram | 2019-01-18 | 2 | -20/+20 |
| | |||||
* | 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 |
| | |||||
* | 4932 | Kartik Agaram | 2019-01-16 | 14 | -836/+1443 |
| | |||||
* | 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 | 7 | -428/+528 |
| | |||||
* | 4927 | Kartik Agaram | 2019-01-14 | 8 | -39/+306 |
| | |||||
* | 4926 | Kartik Agaram | 2019-01-14 | 7 | -223/+355 |
| | |||||
* | 4925 | Kartik Agaram | 2019-01-14 | 10 | -485/+796 |
| | |||||
* | 4924 | Kartik Agaram | 2019-01-14 | 1 | -0/+42 |
| | | | | Restore update_html | ||||
* | 4923 | Kartik Agaram | 2019-01-12 | 11 | -350/+310 |
| | | | | | We want slice-equal? for length-prefixed strings, not null-terminated "kernel" strings. | ||||
* | 4922 | Kartik Agaram | 2019-01-11 | 2 | -12/+13 |
| | |||||
* | 4921 | Kartik Agaram | 2019-01-11 | 13 | -1120/+1203 |
| | |||||
* | 4920 | Kartik Agaram | 2019-01-11 | 13 | -520/+1157 |
| | |||||
* | 4919 | Kartik Agaram | 2019-01-10 | 11 | -2222/+2739 |
| | |||||
* | 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"? | ||||
* | 4914 | Kartik Agaram | 2019-01-07 | 15 | -444/+1575 |
| | |||||
* | 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 |
| | |||||
* | 4910 | Kartik Agaram | 2019-01-06 | 1 | -4/+4 |
| | |||||
* | 4909 | Kartik Agaram | 2019-01-05 | 2 | -19/+32 |
| | | | | Improve error checking to warn on unexpected displacements as well. | ||||
* | 4908 | Kartik Agaram | 2019-01-05 | 8 | -4/+41 |
| | | | | | | | | Fix CI. a) Update canonical binaries. b) Fix an out-of-bounds access in `clear-stream`. This also required supporting a new instruction in `subx run` to load an imm8 into rm8. | ||||
* | 4907 | Kartik Agaram | 2019-01-04 | 1 | -2/+2 |
| | |||||
* | 4906 - helper to allocate streams on the heap | Kartik Agaram | 2019-01-04 | 2 | -0/+175 |
| | |||||
* | 4905 - safe ptr lookup is now 6 instructions | Kartik Agaram | 2019-01-04 | 2 | -25/+20 |
| | | | | | | | | | | | | | The lines within '{}' can now be turned into a macro like `E_X = deref(E_X)`, parameterizing the register being modified. Assumes the input is in a register but also saved elsewhere, so it's safe to clobber and replace with the result. Compare commit 4894. Used to take 9 instructions, 8 of them making loads/stores. Now it's 6 instructions, 4 of them loads/stores (the one non-local load is unchanged, of course). Key is to not consume more registers so we don't have to push/pop them. | ||||
* | 4904 | Kartik Agaram | 2019-01-04 | 1 | -1/+0 |
| | |||||
* | 4903 | Kartik Agaram | 2019-01-03 | 1 | -2/+0 |
| | |||||
* | 4902 - initial sketch, stage 2 of compiler | Kartik Agaram | 2019-01-03 | 1 | -0/+164 |
| | | | | I've agonized over this for a week; high time I saved a snapshot. | ||||
* | 4901 | Kartik Agaram | 2019-01-03 | 6 | -0/+0 |
| | |||||
* | 4900 | Kartik Agaram | 2018-12-30 | 3 | -392/+381 |
| | | | | | | | | | | | Finally really fix the CI failure of commit 4894. This is a remainder to forget my knowledge of stack addresses in the SubX VM when writing SubX programs. Otherwise my programs will work in the VM but not natively. The only assumptions a SubX program should make about its segment addresses are what's encoded in the ELF binary. Thanks to https://en.wikipedia.org/wiki/Address_space_layout_randomization, it can't know anything else. | ||||
* | 4899 | Kartik Agaram | 2018-12-30 | 31 | -158/+160 |
| | | | | Bug in my linkify tool introduced in commit 4891. | ||||
* | 4898 | Kartik Agaram | 2018-12-30 | 4 | -4/+4 |
| |