| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
subx: 'call' and 'return' instructions
|
|
|
|
|
| |
subx: extract helpers for 'push' and 'pop'. We will be using them in
'call' and 'ret' as well.
|
|
|
|
| |
subx: 'pop'
|
|
|
|
|
| |
subx: correct a 'copy' ('mov') instruction as well to get its operand
right from the opcode.
|
| |
|
|
|
|
|
|
|
|
| |
subx: correct 'push' register. It gets its operand right from the
opcode, not a new modrm byte.
Have I misinterpreted any other instructions in this manner (`+rd` in
the Intel manual)?
|
|
|
|
| |
subx: 'pop'
|
| |
|
|
|
|
|
| |
Stop hyperlinking every `i` in subx html files to the integer register
union.
|
| |
|
|
|
|
| |
subx: unconditional 'jump'
|
| |
|
|
|
|
| |
subx: 'mov'
|
|
|
|
|
|
| |
I spent a while spelunking into the code generated by C compilers before
realizing that ignoring the order of arguments for 'cmp' instructions
clarifies everything.
|
|
|
|
|
|
| |
subx: 'compare'
Hopefully I've implemented the 'sense' of comparisons right..
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Hacky one-time html rendering for a single layer in subx.
|
| |
|
|
|
|
|
| |
Undo commit 4002 for factorial.mu, because index.html describes it as an
example showing the labels '{' and '}'.
|
|
|
|
|
| |
Allow list `push` operation to save result in a new list rather than
mutate the existing list.
|
| |
|
| |
|
|
|
|
| |
https://www.reddit.com/r/ProgrammingLanguages/comments/727va7/a_comparison_of_lisps/dnh2q6u
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This regression was (also) introduced by commit 3902 in June.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Narrow the scope of implicit type conversions. Now only numbers can be
freely converted to from other scalars (booleans, characters). We want
in particular to make this an error:
x:character <- new [abc]
|
|
|
|
|
| |
Yet another regression, this time cascading from commit 3953. My
scenario wasn't actually testing what I thought it was testing.
|
|
|
|
|
| |
Don't refresh entire sandbox side when toggling the expected result for
a single sandbox.
|
|
|
|
|
|
|
| |
Don't unnecessarily write sandboxes to disk on F4.
This seems to save almost 20% time when processing a large lesson
directory with 36 sandboxes.
|
|
|
|
|
|
|
|
| |
Improvement on fix 3957: rather than put a band-aid over a slow
operation, eliminate the slowdown entirely.
In this case it turns out we're unnecessarily saving files to disk when
they could never be modified. Are we doing this on F4 as well?!
|
|
|
|
|
| |
Marking sandbox responses as expected can take a long time if there are
many sandboxes. Indicate when a click is being worked on.
|