about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 4028Kartik K. Agaram2017-10-122-7/+7
|
* 4027Kartik K. Agaram2017-10-121-0/+249
| | | | Hacky one-time html rendering for a single layer in subx.
* 4026Kartik K. Agaram2017-10-122-29/+35
| | | | | | | | | | Make memory a sparse map rather than contiguous vector. In the process, a bugfix for `load_program`: support multiple lines of comments. Also save a local copy of the x86 cheatsheet I've been using: https://net.cs.uni-bonn.de/fileadmin/user_upload/plohmann/x86_opcode_structure_and_instruction_overview.pdf
* 4025Kartik K. Agaram2017-10-111-0/+1
| | | | Fix CI.
* 4024 - attempt to get CI working for SubXKartik K. Agaram2017-10-111-0/+1
|
* 4023Kartik K. Agaram2017-10-111-4/+4
|
* 4022Kartik K. Agaram2017-10-111-2/+4
|
* 4021Kartik K. Agaram2017-10-111-2/+2
|
* 4020Kartik K. Agaram2017-10-111-0/+1
|
* 4019Kartik K. Agaram2017-10-111-4/+4
|
* 4018Kartik K. Agaram2017-10-111-3/+3
|
* 4017Kartik K. Agaram2017-10-111-6/+6
|
* 4016 - include subx/ tests in CIKartik K. Agaram2017-10-115-18/+32
|
* 4015Kartik K. Agaram2017-10-112-6/+3
|
* 4014 - core skeleton for x86 interpreterKartik K. Agaram2017-10-113-16/+180
|
* 4013Kartik K. Agaram2017-10-113-4/+8
|
* 4012Kartik K. Agaram2017-10-101-0/+6
|
* 4011 - start of sub-x86 VMKartik K. Agaram2017-10-096-37/+44
|
* 4010Kartik K. Agaram2017-10-042-31/+31
|
* 4009Kartik K. Agaram2017-10-042-19/+28
| | | | | Undo commit 4002 for factorial.mu, because index.html describes it as an example showing the labels '{' and '}'.
* 4008Kartik K. Agaram2017-09-2517-1291/+1305
| | | | | Allow list `push` operation to save result in a new list rather than mutate the existing list.
* 4007Kartik K. Agaram2017-09-252-4/+4
|
* 4006Kartik K. Agaram2017-09-242-54/+52
|
* 4005Kartik K. Agaram2017-09-242-99/+107
| | | | https://www.reddit.com/r/ProgrammingLanguages/comments/727va7/a_comparison_of_lisps/dnh2q6u
* 4004Kartik K. Agaram2017-09-232-2/+2
|
* 4003Kartik K. Agaram2017-09-2344-2169/+2135
|
* 4002Kartik K. Agaram2017-09-234-72/+39
|
* 4001Kartik K. Agaram2017-09-182-2/+2
|
* 4000Kartik K. Agaram2017-09-151-0/+1
|
* 3999Kartik K. Agaram2017-09-152-6/+6
|
* 3998Kartik K. Agaram2017-09-131-427/+444
|
* 3997Kartik K. Agaram2017-09-131-2/+2
| | | | | | | Follow-up to commit 3993: deep-copy needs to also ignore screen and console objects. Basically channels and any fake objects passed into tests. (The real ones will be null, which will work fine thanks to the bugfix of commit 3996.)
* 3996Kartik K. Agaram2017-09-131-1/+18
|
* 3995Kartik K. Agaram2017-09-137-689/+742
|
* 3994Kartik K. Agaram2017-09-131-5/+5
|
* 3993Kartik K. Agaram2017-09-132-30/+84
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fully isolate routines from their arguments. I still need exceptions for containers that are *designed* to be shared between routines. The primary such case is channels; we need some way to share them between routines, and if we deep-copy them that defeats their entire purpose. A milder case is the use of fake file-systems in tests, though that's a hint that there'll be more of these as the OS gets more fleshed out. The pattern seems to be that we need to not deep-copy containers that contain lock fields, and so their operations internally do their own locking. We may have to stop hard-coding the list of exceptions and allow people to define new ones. Perhaps don't deep-copy any container with metadata of 'shared', and then ensure that get-location is only ever called on shared containers. This still isn't absolutely ironclad. People can now store something into a channel and then pass it into a routine to share arbitrary data. But perhaps the goal isn't to be ironclad, just to avoid easy mistakes. I'd still want an automated check for this, though. Some way to highlight it as an unsafe pattern. This completes step 1 in the plan of commit 3992 for making continuations safe.
* 3992Kartik K. Agaram2017-09-101-2/+1
|
* 3991 - start work on making continuations safeKartik K. Agaram2017-09-104-0/+0
| | | | | | | | | | | | | | | | | Plan: 1. Fix a hole where addresses are shared between routines when passed in as arguments to `start-running`. 2. Switch to a new approach to refcount management: instead of updating refcounts when writing products of instructions by default, increment refcounts inside instructions by default and decrement refcounts in caller. More details in future when I actually implement this. 3. Now we shouldn't need a distinction between `new-default-space` and `local-scope`, and all functions can simply decrement refcounts of their default-space, consistently handling any refcounts in the space. At this point if all goes well, continuations should be safe! This commit is just preparation for step 1.
* 3990Kartik K. Agaram2017-09-0340-515/+776
|
* 3989Kartik K. Agaram2017-09-011-19/+19
|
* 3988Kartik K. Agaram2017-09-011-3/+6
|
* 3987Kartik K. Agaram2017-09-019-19/+21
|
* 3986 - bring back delimited continuationsKartik K. Agaram2017-08-302-1/+189
| | | | | | | | | | | | | | | | They're back after a long hiatus: commit 2295 in Oct 2015. I'm not convinced anymore that this is actually a correct implementation of continuations. Issues on at least two fronts: a) These aren't safe yet. Since continuations can be called multiple times, we need to disable reclamation of locals inside a continuation. There may be other type- or memory-safety issues. However, delimited continuations at least seem possible to make safe. Undelimited continuations (call/cc) though are permanently out. b) They may not actually be as powerful as delimited continuations. Let's see if I can build 'yield' out of these primitives.
* 3985Kartik K. Agaram2017-08-302-120/+116
|
* 3984 - bugfix: display errors when scrolling recipe sideKartik K. Agaram2017-08-252-733/+809
| | | | This regression was (also) introduced by commit 3902 in June.
* 3983Kartik K. Agaram2017-08-2212-1823/+1885
|
* 3982 - bugfix: clear old recipe errors on F4Kartik K. Agaram2017-08-222-0/+60
| | | | | | This regression was introduced by commit 3902 in June. Making this commit clean took the last 4 commits of reorganizing.
* 3981Kartik K. Agaram2017-08-222-7/+4
| | | | | It's always been ugly that I referred to a later layer/feature in a label name.
* 3980Kartik K. Agaram2017-08-2212-123/+123
|
* 3979Kartik K. Agaram2017-08-221-4/+4
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-24 16:04:42 +0000