1
0
mirror of https://gitlab.com/camelot/kickc.git synced 2024-12-22 06:29:23 +00:00
KickC is a C-compiler for 6502-based platforms creating optimized and readable assembler code. The language is 95% standard C with a few limitations and a few extensions. Download Releases here https://gitlab.com/camelot/kickc/-/releases
Go to file
2021-05-16 10:19:21 +02:00
.idea Added a test for OutputFileManager. This fixes the problem with -o not being honored always. Closes #644 2021-05-15 12:38:53 +02:00
repo
src Moved stack call parameter assignments out of pass 0. Added address-of handling for procedures converting them to stack call if they have parameters. #121 2021-05-16 10:19:21 +02:00
.gitattributes
.gitignore
.gitlab-ci.yml
CONTRIBUTING.md
kickc.iml
LICENSE.txt
Makefile
NOTICE.txt
pom.xml
README.md

KickC - Optimizing C-compiler for 6502 platforms

KickC is a C-compiler for 6502-based platforms creating optimized and readable assembler code.

The language is 95% standard C with a few limitations, and a few extensions to ensure an optimal fit for creating 6502 assembler code.

The KickC-compiler includes all necessary linker and header files to makes it easy to create and test binaries for the following 6502-based platforms out-of-the-box:

  • Commodore VIC 20
  • Commodore 64
  • Commodore Plus/4 (Commodore 16 , Commodore 116)
  • Atari 2600
  • Atari XL/XE
  • Nintendo NES
  • MEGA65
  • Commander X16

KickC uses the very versatile Kick Assembler. The KickC Compiler produces assembler code for the MOS Technology 6502 processor family. Specifically the compiler supports 6502, 65C02, 65CE02 and 45GS02 CPUs.

Resources

  • Download the newest Release

  • Read the Reference Manual

  • Look through the Source Code

  • Follow the features being developed

  • Discuss the compiler and receive news on facebook

  • Chat on discord

  • Contribute to the development of KickC

BETA

KickC is currently in beta, and at times crash or creates ASM code that does not work properly. Feel free to test it and report any problems or errors you encounter, but do not expect it to produce production quality code. Also, be prepared that breaking changes (to syntax, to semantics, etc.) may be implemented in the next versions.