about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 4962Kartik Agaram2019-02-141-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.
* 4961Kartik Agaram2019-02-1431-209/+253
|
* 4960Kartik Agaram2019-02-132-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.
* 4959Kartik Agaram2019-02-133-105/+142
| | | | | 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 farKartik Agaram2019-02-111-0/+16
| | | | (excluding tests)
* 4957Kartik Agaram2019-02-119-1477/+2007
|
* 4956Kartik Agaram2019-02-112-1/+69
|
* 4955Kartik Agaram2019-02-108-20/+380
| | | | Starting to build up Phase 2 (apps/pack) out of recently designed primitives.
* 4954Kartik Agaram2019-02-109-39/+141
|
* 4953Kartik Agaram2019-02-0521-2139/+3012
|
* 4952Kartik Agaram2019-02-059-13/+474
|
* 4951Kartik Agaram2019-02-0316-78/+273
| | | | Cleaner way to compare streams in tests.
* 4950Kartik Agaram2019-02-0315-0/+0
|
* 4949Kartik Agaram2019-02-0224-42/+62
|
* 4948Kartik Agaram2019-02-023-577/+1588
| | | | | This seems like the final helper we need for Phase 2. Now to build the business logic itself.
* 4947Kartik Agaram2019-02-012-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.
* 4946Kartik Agaram2019-02-012-2/+66
|
* 4945Kartik Agaram2019-02-017-0/+70
|
* 4944Kartik Agaram2019-01-301-4/+4
| | | | Improve syntax highlighting in the Readme.
* 4943Kartik Agaram2019-01-302-3/+2
|
* 4942Kartik Agaram2019-01-214-324/+337
|
* 4941Kartik Agaram2019-01-211-4/+17
|
* 4940Kartik Agaram2019-01-211-4/+4
|
* 4939Kartik Agaram2019-01-213-3/+253
|
* 4938Kartik Agaram2019-01-208-721/+729
|
* 4937Kartik Agaram2019-01-208-452/+1282
|
* 4936Kartik Agaram2019-01-182-20/+20
|
* 4935Kartik Agaram2019-01-161-2/+2
|
* 4934Kartik Agaram2019-01-164-6/+6
|
* 4933Kartik Agaram2019-01-167-50/+50
|
* 4932Kartik Agaram2019-01-1614-836/+1443
|
* 4931Kartik Agaram2019-01-161-1/+0
|
* 4930Kartik Agaram2019-01-157-2/+231
|
* 4929Kartik Agaram2019-01-1515-57/+28
| | | | Clean up primitives for converting from/to hex chars.
* 4928Kartik Agaram2019-01-147-428/+528
|
* 4927Kartik Agaram2019-01-148-39/+306
|
* 4926Kartik Agaram2019-01-147-223/+355
|
* 4925Kartik Agaram2019-01-1410-485/+796
|
* 4924Kartik Agaram2019-01-141-0/+42
| | | | Restore update_html
* 4923Kartik Agaram2019-01-1211-350/+310
| | | | | We want slice-equal? for length-prefixed strings, not null-terminated "kernel" strings.
* 4922Kartik Agaram2019-01-112-12/+13
|
* 4921Kartik Agaram2019-01-1113-1120/+1203
|
* 4920Kartik Agaram2019-01-1113-520/+1157
|
* 4919Kartik Agaram2019-01-1011-2222/+2739
|
* 4918Kartik Agaram2019-01-104-4/+4
|
* 4917Kartik Agaram2019-01-101-140/+0
|
* 4916Kartik Agaram2019-01-1012-24/+611
| | | | | In the process of building slice primitives I found an out-of-bounds access in write-byte.
* 4915Kartik Agaram2019-01-084-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"?
* 4914Kartik Agaram2019-01-0715-444/+1575
|
* 4913Kartik Agaram2019-01-077-2/+472
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-25 08:08:23 +0000