about summary refs log tree commit diff stats
path: root/html
Commit message (Collapse)AuthorAgeFilesLines
* 5125Kartik Agaram2019-04-251-4/+5
|
* 5124Kartik Agaram2019-04-232-2/+2
|
* 5123Kartik Agaram2019-04-231-963/+959
|
* 5122Kartik Agaram2019-04-231-4/+4
|
* 5121Kartik Agaram2019-04-231-1/+1
|
* 5119Kartik Agaram2019-04-2315-10307/+11549
|
* 5081Kartik Agaram2019-04-115-476/+444
|
* 5077Kartik Agaram2019-04-1018-4475/+9025
|
* 5035Kartik Agaram2019-03-291-1848/+2023
|
* 5033Kartik Agaram2019-03-2945-9421/+12048
|
* 4989Kartik Agaram2019-02-2531-2038/+2136
|
* 4982Kartik Agaram2019-02-1860-12259/+12251
|
* 4968Kartik Agaram2019-02-141-635/+911
|
* 4967Kartik Agaram2019-02-1425-4338/+4387
|
* 4959Kartik Agaram2019-02-131-93/+112
| | | | | 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.
* 4957Kartik Agaram2019-02-119-1477/+2007
|
* 4953Kartik Agaram2019-02-0521-2139/+3012
|
* 4948Kartik Agaram2019-02-021-571/+1247
| | | | | This seems like the final helper we need for Phase 2. Now to build the business logic itself.
* 4942Kartik Agaram2019-01-214-324/+337
|
* 4938Kartik Agaram2019-01-201-677/+672
|
* 4937Kartik Agaram2019-01-201-443/+850
|
* 4936Kartik Agaram2019-01-181-19/+19
|
* 4932Kartik Agaram2019-01-1614-836/+1443
|
* 4928Kartik Agaram2019-01-141-425/+475
|
* 4927Kartik Agaram2019-01-141-27/+160
|
* 4926Kartik Agaram2019-01-141-219/+285
|
* 4925Kartik Agaram2019-01-142-456/+611
|
* 4923Kartik Agaram2019-01-122-282/+283
| | | | | We want slice-equal? for length-prefixed strings, not null-terminated "kernel" strings.
* 4922Kartik Agaram2019-01-111-6/+7
|
* 4921Kartik Agaram2019-01-1112-1118/+1201
|
* 4920Kartik Agaram2019-01-113-337/+690
|
* 4919Kartik Agaram2019-01-1011-2222/+2739
|
* 4914Kartik Agaram2019-01-0715-444/+1575
|
* 4901Kartik Agaram2019-01-033-0/+0
|
* 4900Kartik Agaram2018-12-301-353/+347
| | | | | | | | | | | 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.
* 4899Kartik Agaram2018-12-3030-156/+156
| | | | Bug in my linkify tool introduced in commit 4891.
* 4898Kartik Agaram2018-12-302-2/+2
|
* 4897Kartik Agaram2018-12-304-400/+564
|
* 4895Kartik Agaram2018-12-3027-48/+48
|
* 4892Kartik Agaram2018-12-301-12/+15
|
* 4891Kartik Agaram2018-12-30183-341/+524
| | | | | | | | | | | Couple more tweaks to html rendering: a) SubX definitions no longer link redundantly to themselves. This long-standing issue turns out to be tractable to solve for SubX files since the syntax is so simple. b) Fix links to SubX definitions in other directories. I forgot that I have to always generate tags from the directory of the file being linkified. c) Fix link colors. Before we lost all syntax highlighting for functions and Globals. Now they maintain their colors, just add an underline.
* 4890 - new html renderingsKartik Agaram2018-12-29187-5628/+5327
| | | | | | | a) Switch to a light background. b) Linkify calls in .subx files. c) Keep all colorization in the Vim colorscheme, get rid of hacky special-cases in update_html.
* 4880Kartik Agaram2018-12-2823-42/+40
|
* 4879Kartik Agaram2018-12-286-32/+32
|
* 4878Kartik Agaram2018-12-271-1/+1
|
* 4877Kartik Agaram2018-12-271-2/+2
|
* 4869Kartik Agaram2018-12-1642-1210/+1195
|
* 4865Kartik Agaram2018-12-101-14/+14
| | | | More mnemonic register usage in write-stream.
* 4864Kartik Agaram2018-12-101-213/+266
| | | | Our first buffer overflow!
* 4863Kartik Agaram2018-12-102-2/+2
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-06-16 10:27:42 +0000