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
jespergravgaard be1f1a419b Attempt at adding C-formatting. 2019-04-20 22:47:18 +02:00
.idea try again update test reference. maven config for tests in parallel. 2019-04-02 21:41:57 -04:00
repo/cml/kickass/kickassembler Added local folder repository 2018-02-12 22:26:15 +01:00
src Now optimizing *(ptr+n) into ptr[n] when possible. 2019-04-20 22:12:56 +02:00
.gitattributes Attempt at adding C-formatting. 2019-04-20 22:47:18 +02:00
.gitignore Added .ds_store 2018-03-28 10:29:14 +02:00
.gitlab-ci.yml Added some maven debugging 2018-11-08 00:08:11 +01:00
CONTRIBUTING.md Update CONTRIBUTING.md 2019-04-02 20:12:23 +00: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
README.md Update README.md 2019-04-19 19:35:44 +00:00
kickc.iml Updated libraries. Added packaging assembly to maven POM. 2018-09-26 19:57:15 +02:00
pom.xml change maven parallelization setting 2019-04-02 22:06:32 -04:00

README.md

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.