| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | |
| | |
| | |
| | | |
One more instruction where I forgot to update the carry flag.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
How did things seem to be working until now?
- We were saving an address from the stack to stream.read
- When we read this address in skip-chars-matching:loop, we used to stop early
But now we've moved the stack to a larger address, one where the most significant
byte is set. When the stack address now gets to skip-chars-matching:loop,
it's treated as a negative number and we proceed through the loop. At which
point we try to index into the array using it.
No real test to be written to protect against this :(
|
| | | |\
| | |/
| |/|
| | |
| | | |
dquotes.subx is now segfaulting after this merge. Seems to be trying to
use addresses from the old stack.
|
| | |\ \
| |/ /
|/| | |
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Start computing the Carry Flag (CF) everywhere
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Skimping on tests; the code changes seem pretty trivial. Will this fix
CI?!
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Standardize layout of some code fragments, and fix several bugs in computing
the overflow flag in the process. a64 = b32 + c32 doesn't benefit from
`a` being 64-bit without casting `b`.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Make the first instruction described something that doesn't touch flags,
so we don't introduce too much complexity all at once.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This is time-consuming mostly for me to come up with example scenarios
testing all the different combinations of flags.
|
| | | | |
| | | |
| | | |
| | | | |
Correct some confusing log messages.
|
| | | | |
| | | |
| | | |
| | | | |
Inline some macro definitions.
|
| | | | |
| | | |
| | | |
| | | | |
Drop some prints as a first step to straightening things out.
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Tests failing.
This approach seems wrong. I'm not sure even the tests are correct. Also,
some open questions:
1. Should setting the overflow flag always set the carry flag?
2. Should the carry flag only be set on add/subtract/compare, or by all
arithmetic ops?
3. Had to turn off the -ftrapv flag in `build`. Is there a way to detect
overflow without actually causing overflow?
Once we start setting CF correctly we have to implement jump above/below
instructions (8- and 32-bit displacement variants).
https://github.com/akkartik/mu/issues/30
|
| | | |
| | |
| | |
| | |
| | | |
Support allocating more than 0x01000000 bytes (8MB) to a segment in the
VM.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Pretty blunt for now; just abort the entire program on any failure to write.
I'm encountering it because I'm somehow treating a stream address as a
file descriptor. Maybe mmap is returning addresses below 0x08000000?
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Bugfix: I'd neglected to update the input stream's state when natively
writing a stream to file.
|
| | | | |
|
| | | | |
|
| | |\ \
| |/ /
|/| |
| | | |
apps/dquotes still segfaulting on native run.
|
| | |\ \
| | | |
| | | | |
SubX in SubX: Transforming uses of string literals (prerequisite B)
|
| | | | | |
|
| | |/ /
| | |
| | |
| | | |
Emitting the metadata for literal strings.
|
| | | |\
| |_|/
|/| |
| | | |
Segfault in this branch is now fixed.
|
| |\ \ \
| | | |
| | | | |
Build `allocate` out of `mmap`
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
All tests passing now. Things are very explicit; before a program can `allocate`
memory, it has to first obtain a segment from the OS using `new-segment`.
|
| | | | |
| | | |
| | | |
| | | | |
Tests still failing. Passing until layer 53.
|
| | | | |
| | | |
| | | |
| | | | |
Tests still broken.
|
| |/ / /
| | |
| | |
| | |
| | | |
Snapshot of incomplete work to have the memory allocator use `mmap` rather
than `brk`. C tests pass, but the SubX layers are still broken.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Pull in some final stylistic and debugging-friendly tweaks from my old
version of commit 5132 and earlier.
|
| | | |
| | |
| | |
| | |
| | | |
We'll just loudly abort the entire program if the output stream isn't large
enough to accept all the characters we want to print.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Hoist address computation out of the loop.
I'm giving in to the temptation to optimize here, and violating my own
rule of minimizing local variables by introducing 'curr'. My fig leaf is
that the number of instructions inside the loop goes down, and duplicating
inside the loop may be distracting to readers.
|
| | | |
| | |
| | |
| | | |
Another minor stylistic point: I try to use EDI for destination operands.
|