6502/kickc
1
0
Fork 0
mirror of https://gitlab.com/camelot/kickc.git synced 2024-11-22 16:33:48 +00:00
Code Issues Projects Releases Wiki Activity
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
2,364 Commits 45 Branches 31 Tags 374 MiB
Assembly 46.2%
Java 29.4%
C 17.7%
Cython 6.2%
ANTLR 0.2%
Other 0.2%
27d0aa9e67
Go to file
Jesper Gravgaard 27d0aa9e67 Improved VERA code.
2021-01-04 12:26:13 +01:00
.idea Added a few missing fragments. Improved fragments for if() where rvalue1==0. Closes #598 2020-12-12 00:48:31 +01:00
repo
src Improved VERA code. 2021-01-04 12:26:13 +01:00
.gitattributes
.gitignore
.gitlab-ci.yml
CONTRIBUTING.md
kickc.iml Updated to ANTLR4.9. Merged Andrzej Śliwa implementation of __address() support for constant expressions branch address_with_expression_value. Closes !1 2020-12-11 01:18:36 +01:00
LICENSE.txt
Makefile Added Makefile for ease of use. Closes #520 2020-09-28 00:10:11 +02:00
NOTICE.txt
pom.xml Updated to ANTLR4.9. Merged Andrzej Śliwa implementation of __address() support for constant expressions branch address_with_expression_value. Closes !1 2020-12-11 01:18:36 +01:00
README.md Update README.md. Gitlab keeps changing the releases URL. Closes #568 2020-11-09 07:21:33 +00: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.