| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
- The LKD and SKD operations have been removed
- SHF/SHC have been moved to after LDD/STD
- SWP/ROT/DUP/OVR have been rearranged to be DUP/OVR/SWP/ROT
- NOT/AND have been rearranged to be AND/NOT
- PSK has been added, placed after PSH
- SPL has been added, placed after POP
|
| |
|
|
|
|
|
| |
The assembler previously reported only the length of the generated
bytecode in bytes. It now also reports the program size as a percentage
of the maximum program size of 64KB, to give the user an idea of how
close they are to hitting the program size limit.
|
| | |
|
| |
|
|
|
| |
Don't print the internal error representation to the console when an
error occurs while trying to write the assembled bytecode to stdout.
|
| |
|
|
|
|
| |
The JMP and JSR op-codes no longer include a * character, and the
double-mode JCN op-codes have been changed to JSN to reflect a change
in the instruction set of the Bedrock processor.
|
| |
|
|
|
|
| |
When the assembler successfully assembles a program, it will now report
the names of all label definitions for which there are no label references.
This is to aid the user in finding dead code within their programs.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When the assembler encounters an error, the erroneous line and the line
number are output in order to help the user to find where in the input
file the error occurred. This is useful for single-file inputs, but the
line number is generally not helpful if the input file was generated by
concatenating multiple files.
In order to help the user to determine where in the program source the
error occurred, the assembler now reports the name of the label which
directly precedes the erroneous line.
|
| |
|
|
|
|
| |
Double-quoted strings are automatically terminated by null bytes, with
single-quoted strings maintaining the prior non-terminated string
behaviour.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Previously, attempting to write large amounts of bytecode to stdout
would often result in only the first n bytes being written.
|
| |
|
|
|
| |
This will break unix pipelines in order to prevent any emulator down the
pipeline from attempting to run a malassembled program.
|
| | |
|
| | |
|
| | |
|
| |
|
