1
0
mirror of https://gitlab.com/camelot/kickc.git synced 2024-12-25 11:32:07 +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
2020-08-24 22:14:46 +02:00
.idea Upgraded to OpenJDK 14, Junit 5, Surefire 3.0, JaCoCo 0.8.5. 2020-08-24 21:00:16 +02:00
repo/cml/kickass/kickassembler Updated KickAsm 65CE02 to new version. Fixed INW/DEW addressing mode problem. Working on MEGA65 platform target. #507 2020-08-23 20:05:48 +02:00
src Working on handling the missing unzip on the new Docker image. 2020-08-24 22:05:05 +02:00
.gitattributes Attempt at adding C-formatting. 2019-04-20 22:47:18 +02:00
.gitignore Added target files. 2020-05-11 11:04:32 +02:00
.gitlab-ci.yml Working on handling the missing unzip on the new Docker image. 2020-08-24 22:14:46 +02:00
CONTRIBUTING.md Update CONTRIBUTING.md 2019-04-02 20:12:23 +00:00
kickc.iml Upgraded to OpenJDK 14, Junit 5, Surefire 3.0, JaCoCo 0.8.5. 2020-08-24 21:00:16 +02:00
LICENSE.txt Added license 2017-12-31 00:12:09 +00:00
NOTICE.txt Added example of music routines. 2019-03-26 21:27:36 +01:00
pom.xml Upgraded to OpenJDK 14, Junit 5, Surefire 3.0, JaCoCo 0.8.5. 2020-08-24 21:00:16 +02:00
README.md Update README.md 2019-04-19 19:35:44 +00:00

KickC - Optimizing C-compiler for 6502

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

The KickC language is classic C with some limitations, some modifications and some extensions to ensure an optimal fit for creating 6502 assembler code.

  • Download the newest Release

  • Read the Reference Manual

  • Look through the Source Code

  • Follow the open/closed features being developed

  • Discuss the compiler and receive news on facebook

  • 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.