shazz/shazzam

Issues

• Support VASYL / Beamracer

  #17 opened 4 years ago by shazz
  0

• Crunchers related issues

  #3 opened 4 years ago by shazz
  0

• Improve CLI (colors, errors, logging...)

  #28 opened 4 years ago by shazz
  0

• Add gfx plugins for Koala,...

  #21 opened 4 years ago by shazz
  0

• Docs related issues

  #4 opened 4 years ago by shazz
  0

• Missing assembler directives:

  #27 opened 4 years ago by shazz
  0

• Build related issues

  #5 opened 4 years ago by shazz
  0

• Debugger session to trace generated code line by line

  #22 opened 4 years ago by shazz
  0

• Examples related issues

  #9 opened 4 years ago by shazz
  0

• Tests related issues

  #6 opened 4 years ago by shazz
  0

• Add support for c64jasm

  #23 opened 4 years ago by shazz
  0

• Ability to split shazzam code in multiple files

  #16 opened 4 years ago by shazz
  0

• Tooling related issues

  #8 opened 4 years ago by shazz
  0

• Refactor set_prefs

  #26 opened 4 years ago by shazz
  0

• Replace some dict by bidict, especially for address / labels mapping

  #19 opened 4 years ago by shazz
  0

• Macros related issues

  #7 opened 4 years ago by shazz
  0

• Add optional basic upstart

  #25 opened 4 years ago by shazz
  0

• CODE segment size incorrect (2 bytes missing) in fun_with_macro example

  #13 opened 4 years ago by shazz
  0

• Relative backward address not well computed

  #24 opened 4 years ago by shazz
  0

• CC65 segment configuration is invalid if one segment < 0x0801

  #20 opened 4 years ago by shazz
  0

• Override __str__ on opcode function to allow or avoid nop instead of nop().. or rts instead of rts() !!!

  #12 opened 4 years ago by shazz
  0

• If 2 blocks of bytes are following, the second label won't appear

  #2 opened 4 years ago by shazz
  0

• Add support for unofficial 6502 opcodes

  #18 opened 4 years ago by shazz
  0

• Add in generated headers: DO NOT MODIFY

  #14 opened 4 years ago by shazz
  0

• Generate CC65 Makefile

  #15 opened 4 years ago by shazz
  0

• Change add_instruction() return

  #10 opened 4 years ago by shazz
  0

• if 2 labels have the same address, they won't be added to the assembly code

  #11 opened 4 years ago by shazz
  0

• If global labels are shown in asm code instead of addresses, CC65 cannot find them

  #1 opened 4 years ago by shazz
  0