| Age | Commit message (Collapse) | Author |
|---|
|
No implementations yet
|
|
|
|
Pretty simple tokeniser, doesn't do a lot and needs to error check better.
|
|
If an empty file is read, we want to deal with it in later user code
rather than just failing immediately.
|
|
|
|
Easier to write includes now just using < with the module name, in
comparison to using relative paths.
|
|
|
|
|
|
|
|
Changed folder names for sake of clarity (will be introducing a new
build target soon), and Makefile can now easily support more targets.
|
|
|
|
Performs a jump when the (BYTE|HWORD|WORD) at the top of the stack is
non zero.
|
|
Checks if the operand given is a well defined program address, then
performs the jump.
|
|
This is because we just OR the bits into the specific byte of the
word. This means the previous state may leave artefacts as the OR
doesn't clear the bits away.
To do so, we apply a bit mask to clear the specified byte(s) of the
word, then perform the OR.
|
|
|
|
First the program, then the registers then the stack.
|
|
Prints an error message, returns a non zero code based on error
code (255 - err).
In main, I propagate this exit code.
|
|
This is simply a program with an embedded set of instructions which
indefinitely computes and prints fibonacci numbers, computing them in
pairs.
Does it completely through the virtual machine rather than just hard C
instructions.
Also amended the Makefile to compile it. Required moving the main.c
object file into the dependencies of $(DIST)/$(OUT).
I should track the dependencies for fib.c and main.c as well.
|
|
Also fixed an overflow error in vm_dup_word, where I underflow the
index of vm->stack.data which causes a buffer overflow.
|
|
Here is where we may have differing interpretations of what the bits
in the data pile may actually mean. This in particular refers to
printing the signed or unsigned versions of the bits given. Also,
interpreting some byte as a character or just a raw number.
|
|
Only happens when vm_print_program(STDERR), as STDERR occurs before
STDOUT on Emacs. So while the lines would print, no instructions
would follow. This fixes that by using fp.
|
|
Was only used for OP_PUSH data types anyway, so is essentially
useless. Only OP_PUSH has operands after it that directly relate to
it: the rest either have a fixed type (a byte for registers, for
example) or NIL (because they have no operand).
|
|
Routines that use the stack for their operands i.e. aren't supplied
operands directly all have the same signature. We may as well stick
them all together in one array and one conditional, just reduces the
number of branches. Also looks nicer.
Implemented OP_PLUS_*. Pretty simple to implement.
Deleted vm_peek as it was only necessary to update the `ret` register.
|
|
Takes two operands from the stack then pushes their sum.
|
|
|
|
Every vm routine now returns an err_t, which is an enumeration of
possible error states. ERR_OK represents the good state and is 0 so
error checking seems very natural in terms of language `if (err) ...`.
Errors bubble up the runtime, with any callers forced to check if an
error occurred.
This does mean that routines that call other routines cannot provide
an accurate trace of the subcaller (based on the fact that an error is
generated for the current instruction), but this should be a non issue
as no instruction should be complex enough to need proper traces.
|
|
Uses the stack and register, respectively, to jump to an absolute
address. The stack based jump pops a word off the stack to perform a
jump, while the register based one uses the operand to figure out
which register to use.
|
|
Wasn't useful or necessary.
|
|
Jumps to the operand given, interpreted as a word, an absolute
address.
|
|
This adds a bound on vm_execute_all to stop program->ptr from going
past program->max.
|
|
|
|
Wasn't very secure for endianness, and using these helpers abstracts
the details away a bit in case I want to enforce a certain system.
|
|
If I add a new operand I want the build system to be more helpful in
finding the places I need to change to make it work.
|
|
Duplicates the nth datum off the stack, pushing it to the top. Useful
for operations such as MOV which eat the stack.
|
|
Use (H)WORD_SIZE more, added some notes, etc
|
|
Uses memcpy internally, so we don't need to care about endianness.
|
|
|
|
This is because we were checking them as if they were word registers.
|
|
|
|
Also split out the check for whether $(DIST) exists by making it its
own recipe. Removes the repeated checks in each object compilation.
|
|
For each cycle, print the cycle and any changes. We track changes on
the stack by remembering the previous stack pointer. For registers, I
remember the previous array of registers and do a byte level compare
of the current registers and the remembered ones.
Produces pretty log messages and an easy way to track execution.
|
|
Easier to read now
|
|
|
|
Will be used to provide traces during program execution or assembly.
|
|
|
|
Prints the opcode then any operands in the following brackets
|
|
Instead of making routines to handle data in the `ret` register, just
store the result of POP into the last word register.
This means we are no longer using vm_pop_* or POP_ROUTINES for the
vm_execute script on OP_POP: instead we'll just use vm_mov_* which
automatically pops the datum for us, while moving the datum to the
last register.
|
|
|
|
|
|
|
