6502/SixtyPical
1
0
Fork 0
mirror of https://github.com/catseye/SixtyPical.git synced 2024-06-26 16:29:28 +00:00
Code Issues Projects Releases Wiki Activity
A 6502-oriented low-level programming language supporting advanced static analysis
259 Commits 1 Branch 23 Tags 1.3 MiB
Python 98.2%
Shell 1.5%
xBase 0.3%
bef1aba8ce
Go to file
Chris Pressey bef1aba8ce Do not assume every label refers to a word-sized chunk of memory.
2017-12-11 10:42:42 +00:00
bin Ability to --debug analysis. Make 16-bit addition test pass. 2017-12-07 11:49:15 +00:00
doc Amend spec with brief description of new behaviour of add. 2017-12-07 15:34:06 +00:00
eg Break the ground where we need to implement word table read/write. 2017-12-08 15:53:18 +00:00
src/sixtypical Do not assume every label refers to a word-sized chunk of memory. 2017-12-11 10:42:42 +00:00
tests We really need to review how storage location labels are emitted. 2017-12-08 16:59:31 +00:00
.gitignore Refactor to replace some sketchy code with code actually in use. 2015-10-16 10:40:38 +01:00
.hgignore Refactor to replace some sketchy code with code actually in use. 2015-10-16 10:40:38 +01:00
.hgtags Added tag 0.6 for changeset f89772f47de9 2015-10-23 16:37:22 +01:00
HISTORY.markdown Break the ground where we need to implement word table read/write. 2017-12-08 15:53:18 +00:00
LICENSE Add TODO to README, update license information. 2015-10-16 10:00:51 +01:00
loadngo.sh Use right endianness when copying literal word into storage. 2017-12-07 16:49:43 +00:00
README.markdown Break the ground where we need to implement word table read/write. 2017-12-08 15:53:18 +00:00
test.sh Add syntax for extern routines, add syntax tests. 2015-10-17 13:50:21 +01:00

README.markdown

SixtyPical

SixtyPical is a very low-level programming language, similar to 6502 assembly, with static analysis through abstract interpretation.

In practice, this means it catches things like

  • you forgot to clear carry before adding something to the accumulator
  • a subroutine that you call trashes a register you thought was preserved
  • you tried to write the address of something that was not a routine, to a jump vector

and suchlike. It also provides some convenient operations and abstractions based on common 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)
  • explicit tail calls
  • indirect subroutine calls

The reference implementation can execute, analyze, and compile SixtyPical programs to 6502 machine code.

SixtyPical is a work in progress. The current released version of SixtyPical is 0.9-PRE (not released yet.)

Documentation

TODO

Operations on 16 bit values

Compare word (constant or memory location) with memory location or pointer. (Maybe?)

And then write a little demo "game" where you can move a block around the screen with the joystick.

vector table type

low and high address operators

To turn word type into byte.

save registers on stack

This preserves them, so that, semantically, they can be used later even though they are trashed inside the block.

And at some point...

  • copy x, [ptr] + y
  • Maybe even copy [ptra] + y, [ptrb] + y, which can be compiled to indirect LDA then indirect STA!
  • Check that the buffer being read or written to through pointer, appears in approporiate inputs or outputs set.
  • initialized byte table memory locations
  • always analyze before executing or compiling, unless told not to
  • trash instruction.
  • interrupt routines.
  • 6502-mnemonic aliases (sec, clc)
  • other handy aliases (eq for z, etc.)
  • have copy instruction able to copy a constant to a user-def mem loc, etc.
  • add absolute addressing in shl/shr, absolute-indexed for add, sub, etc.
  • check and disallow recursion.
  • automatic tail-call optimization (could be tricky, w/constraints?)
  • re-order routines and optimize tail-calls to fallthroughs