6502/SixtyPical
1
0
Fork 0
mirror of https://github.com/catseye/SixtyPical.git synced 2024-11-22 01:32:13 +00:00
Code Issues Projects Releases Wiki Activity
A 6502-oriented low-level programming language supporting advanced static analysis
537 Commits 1 Branch 23 Tags 1.3 MiB
Python 98.2%
Shell 1.5%
xBase 0.3%
0593ce6a66
Go to file
Chris Pressey 0593ce6a66 Move merge_programs() out of main. Handle missing -o options.
2018-09-07 09:26:11 +01:00
bin Move merge_programs() out of main. Handle missing -o options. 2018-09-07 09:26:11 +01:00
doc Add notes for Apple II target. 2018-09-05 12:59:38 +01:00
eg Abort loadngo apple2, if the SixtyPical program couldn't compile. 2018-09-06 12:50:47 +01:00
images
src/sixtypical Move merge_programs() out of main. Handle missing -o options. 2018-09-07 09:26:11 +01:00
tests Explicitly sort the chains by their content, for stable sort. 2018-09-06 17:15:10 +01:00
.gitignore
HISTORY.md Explicitly sort the chains by their content, for stable sort. 2018-09-06 17:15:10 +01:00
LICENSE
loadngo.sh --output cmdline argument, serialize() returns an array of bytes. 2018-09-06 16:18:41 +01:00
README.md Rewrite the intro blurb in the README. 2018-09-05 21:36:18 +01:00
test.sh
TODO.md

README.md

SixtyPical

Version 0.17. Work-in-progress, everything is subject to change.

SixtyPical is a low-level programming language with advanced static analysis. Many of its primitive instructions resemble those of the 6502 CPU — in fact it is intended to be compiled to 6502 machine code — but along with these are constructs which ease structuring and analysizing the code.

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, but you don't want the overhead of compiler-added code 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, 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

Many of these checks are done with abstract interpretation, where we go through the program step by step, tracking not just the changes that happen during a specific execution of the program, but sets of changes that could possibly happen in any run of the program.

SixtyPical also provides some convenient operations based on machine-language programming idioms, such as

  • copying values from one register to another (via a third register when there are no underlying instructions that directly support it); this includes 16-bit values, which are copied in two steps
  • explicit tail calls
  • indirect subroutine calls

SixtyPical is defined by a specification document, a set of test cases, and a reference implementation written in Python 2. The reference implementation can analyze and compile SixtyPical programs to 6502 machine code, which can be run on several 6502-based 8-bit architectures:

  • Commodore 64
  • Commodore VIC-20
  • Atari 2600 VCS
  • Apple II

Quick Start

If you have the VICE emulator installed, from this directory, you can run

./loadngo.sh c64 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:

Screenshot of result of running hearts.60p

You can try the loadngo.sh script 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.

Documentation