Exploring the visualization of 6502 opcodes
Go to file
2022-11-21 10:36:36 -05:00
.github/workflows scala 3.2.1 2022-11-14 12:14:03 -05:00
nescant/src define load and store 2022-09-07 11:25:35 -04:00
project include weaver 2022-11-19 21:49:50 -05:00
scratchpad/src use generated code instead 2022-11-21 10:36:36 -05:00
src define load and store 2022-09-07 11:25:35 -04:00
.gitignore
.scalafix.conf
.scalafmt.conf scalafmt 3.6.1 2022-11-11 14:13:58 -05:00
build.sbt drop fmt on compile 2022-10-16 23:42:16 -04:00
Jenkinsfile
LICENSE
README.md
TODO.md todo 2022-11-19 23:17:02 -05:00

6502-opcodes

Addressing modes

  • Immediate: a value literal
  • ZeroPage: argument is an 8-bit address to the zero page
  • ZeroPageX: argument is an 8-bit address to the zero page, incremented by X without carry
  • ZeroPageY: argument is an 8-bit address to the zero page, incremented by Y without carry
  • Absolute: argument is an 16-bit address
  • AbsoluteX: argument is an 16-bit address, incremented by X with carry
  • AbsoluteY: argument is an 16-bit address, incremented by Y with carry
  • Indirect: argument an address (A); the effective value is an address (B) stored at that address (A); used only by Jump
  • IndirectX: argument is an 8-bit address; find a value at this address incremented by the value X
  • IndirectY: argument is an 8-bit address; find a value at this address; increment the value by Y

TODO - Nescant

  • mappings, enums, and bitfields are enums

TODO

  1. operand support should be derived from enum support
  • postfix operations to accumulator values
  • maybe implement define registry
  • register locking (i.e. disallow X writes during indexed traversal that uses X)
  • compiler optimization
    • when writing multiple, 16-bit address literals to memory, they may share the same high byte. if all writes are done by bouncing off the accumulator, you can save instructions by using the accumulator for the high byte once and writing multiple times
  • articulate AST as different from ASM stream
  • register locking (transactions) via phantom types

Mutation tracking

  • If the injected scope is local to the caller (and not reused), then it is also local to the called method, and can be rendered as a local val declaration

Elsewhere