1
0
mirror of https://gitlab.com/camelot/kickc.git synced 2024-11-22 16:33:48 +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-01-03 20:14:05 +01:00
.idea Added cruncher plug-in and example programs. Closes #603 2020-12-30 23:13:55 +01:00
repo Added cruncher plug-in and example programs. Closes #603 2020-12-30 23:13:55 +01:00
src Fix to problem with two ROL fragments by @SijmenSchoon. Moved NotLiteralException singleton behing a function. Closes #604 2021-01-03 20:14:05 +01:00
.gitattributes
.gitignore Fixed problem where temporary folders not being deleted causes errors on every compile. Closes #493 2020-11-02 15:00:09 +01:00
.gitlab-ci.yml
CONTRIBUTING.md Update CONTRIBUTING.md 2020-08-24 21:32:24 +00:00
kickc.iml Added cruncher plug-in and example programs. Closes #603 2020-12-30 23:13:55 +01:00
LICENSE.txt
Makefile Added Makefile for ease of use. Closes #520 2020-09-28 00:10:11 +02:00
NOTICE.txt Added cruncher plug-in and example programs. Closes #603 2020-12-30 23:13:55 +01:00
pom.xml Added cruncher plug-in and example programs. Closes #603 2020-12-30 23:13:55 +01:00
README.md Update README.md. Gitlab keeps changing the releases URL. Closes #568 2020-11-09 07:21:33 +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.