6502/kickc
1
0
Fork 0
mirror of https://gitlab.com/camelot/kickc.git synced 2024-12-28 16:31:36 +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,270 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%
599aaf4d67
Go to file
jespergravgaard 599aaf4d67 Added test for macro-based struct addressing vs. const-pointer based.
2020-10-19 23:59:26 +02:00
.idea Fixed typo and tests for conio comment 2020-10-17 14:47:29 +01:00
repo/cml/kickass/kickassembler
src Added test for macro-based struct addressing vs. const-pointer based. 2020-10-19 23:59:26 +02:00
.gitattributes
.gitignore Add conio implementation for Atari XL target 2020-10-15 10:18:44 +01:00
.gitlab-ci.yml Testing with OpenJDK 13. 2020-08-24 23:39:21 +02:00
CONTRIBUTING.md Update CONTRIBUTING.md 2020-08-24 21:32:24 +00:00
kickc.iml Fixed typo and tests for conio comment 2020-10-17 14:47:29 +01:00
LICENSE.txt
Makefile Added Makefile for ease of use. Closes #520 2020-09-28 00:10:11 +02:00
NOTICE.txt Updated NOTICE.txt with new licenses. 2020-08-24 23:06:57 +02:00
pom.xml Removed warning when packaging. 2020-08-24 23:52:38 +02:00
README.md

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.