Tree @master (Download .tar.gz)
SixtyPical
Version 0.21 | See also: Bubble Escape 2K ∘ SITU-SOL
NOTE: Having met the majority of its goals, the SixtyPical project might not undergo much more development going forward. See Future directions for SixtyPical for more information.
SixtyPical brings advanced static analysis to the 6502.
SixtyPical is a low-level programming language supporting some advanced static analysis methods. Its reference compiler can generate efficient code for several 6502-based target platforms while catching many common mistakes at compile-time, reducing the time spent in debugging.
Quick Start
Make sure you have Python (2.7 or 3.5+) installed. Then
clone this repository and put its bin directory on your
executable search path. Then you can run:
sixtypical
If you have the VICE emulator suite installed, you can run
sixtypical --run-on=x64 eg/c64/hearts.60p
and it will compile the hearts.60p source code and
automatically start it in the x64 emulator, and you should see:

You can try sixtypical --run-on on other sources in the eg directory
tree, which contains more extensive examples, including an entire
game(-like program); see eg/README.md for a listing.
Features
SixtyPical aims to fill this niche:
- You'd use assembly, but you don't want to spend hours debugging (say) a memory overrun that happened because of a ridiculous silly error.
- You'd use C or some other "high-level" language, but you don't want the extra overhead added by the compiler to manage the stack and registers.
SixtyPical gives the programmer a coding regimen on par with assembly language in terms of size and hands-on-ness, but also able to catch many ridiculous silly errors at compile time.
Low level
Many of SixtyPical's primitive instructions resemble those of the MOS Technology 6502 — it is in fact intended to be compiled to 6502 machine code. However, it also provides some "higher-level" operations based on common 8-bit machine-language programming idioms, including
- copying values from one register to another (via a third register when there are no underlying instructions that directly support it)
- copying, adding, and comparing 16-bit values (done in two steps)
- explicit tail calls
- indirect subroutine calls
While a programmer will find these constructs convenient, their inclusion in the language is primarily to make programs easier to analyze.
Static analysis
The SixtyPical language defines an effect system, and the reference compiler abstractly interprets the input program in the manner of flow typing to confirm that it does not violate it. This can detect common mistakes such as
- you forgot to clear carry before adding something to the accumulator
- a subroutine that you called trashes a register you thought it preserved
- you tried to read or write a byte beyond the end of a byte array
- you tried to write the address of something that was not a routine, to a jump vector
Efficient code
Unlike most conventional languages, in SixtyPical the programmer must manage memory very explicitly, selecting the registers and memory locations to store each piece of data in. So, unlike a C compiler such as cc65, a SixtyPical compiler doesn't need to generate code to handle calling conventions or register allocation. This results in smaller (and thus faster) programs.
The flagship demo, a minigame for the Commodore 64, compiles to
a 930-byte .PRG file.
Target platforms
The reference implementation can analyze and compile SixtyPical programs to 6502 machine code formats which can run on several 6502-based 8-bit architectures:
For example programs for each of these, see eg/README.md.
Specification
SixtyPical is defined by a specification document, a set of test cases, and a reference implementation written in Python.
There are over 400 test cases, written in Falderal format for readability. In order to run the tests for compilation, dcc6502 needs to be installed.
- SixtyPical specification
- Literate test suite for SixtyPical syntax
- Literate test suite for SixtyPical analysis (operations)
- Literate test suite for SixtyPical analysis (storage)
- Literate test suite for SixtyPical analysis (control flow)
- Literate test suite for SixtyPical compilation
- Literate test suite for SixtyPical fallthru optimization
- Literate test suite for SixtyPical callgraph construction
Documentation
Commit History
@master
git clone https://git.catseye.tc/SixtyPical/
- Beginning of: buffers and pointers. Chris Pressey 8 years ago
- Expand on a note in the TODO. Chris Pressey 8 years ago
- Add some notes to the TODO section of the README. Chris Pressey 8 years ago
- Add draft of Design Goals document. Chris Pressey 8 years ago
- Assert that the loop variable is meaningful in repeat. Unit test. Chris Pressey 8 years ago
- Update the spec re what literal integers in the code mean. Chris Pressey 8 years ago
- Add some tests for copying literal words to word memory locations. Chris Pressey 8 years ago
- Support copy'ing a word constant to a word location. Joystick eg. Chris Pressey 8 years ago
- Minor changes to docs. Chris Pressey 8 years ago
- Small edits to spec. Chris Pressey 8 years ago
- Going over the spec for version 0.8-PRE. Chris Pressey 8 years ago
- Start a development branch. Chris Pressey 8 years ago
- Release version 0.7. Chris Pressey 8 years ago
- Minor edit to TODO. Chris Pressey 8 years ago
- Remove low/high byte operators until I've thought about it more. Chris Pressey 8 years ago
- Fix links in README. Chris Pressey 8 years ago
- Add uncommitted example source, and fix names of 2 others. Chris Pressey 10 years ago
- Low and high address operators, parsing and execution thereof. Chris Pressey 10 years ago
- Compile copy byte to byte and word to word. Chris Pressey 10 years ago
- word types, with syntax and analysis thereof Chris Pressey 10 years ago
- Split scanner off from parser module, into own module. Chris Pressey 10 years ago
- Initial value for locations: changed syntax, executes, compiles. Chris Pressey 10 years ago
- Spec and tests for initial values of locations. Chris Pressey 10 years ago
- Added tag 0.6 for changeset f89772f47de9 Chris Pressey 10 years ago
- Prep for release of 0.6. Chris Pressey 10 years ago
- Constants (such as routines) cannot be given in call-constraints. Chris Pressey 10 years ago
- Update HISTORY and README. Chris Pressey 10 years ago
- Fix tests. Chris Pressey 10 years ago
- {Low,High}AddressByte emittables to fix copy, make indirect call! Chris Pressey 10 years ago
- Implement indirect JSRs with trampolines in theory; doesn't work. Chris Pressey 10 years ago