6502/kickc
1
0
Fork 0
mirror of https://gitlab.com/camelot/kickc.git synced 2024-11-23 23:32:55 +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
889 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%
3434a695d2
Go to file
jespergravgaard 3434a695d2 Implemented a bunch of the foundation needed for function pointers - incl. the parser and handling of pointers in zeropage variables.
2019-04-03 00:03:37 +02:00
.idea
repo/cml/kickass/kickassembler
src Implemented a bunch of the foundation needed for function pointers - incl. the parser and handling of pointers in zeropage variables. 2019-04-03 00:03:37 +02:00
.gitignore
.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
kickc.iml
LICENSE.txt
NOTICE.txt Added example of music routines. 2019-03-26 21:27:36 +01:00
pom.xml Added source encoding to Maven POM (to ensure Windows builds work properly). 2019-04-01 08:42:27 +02:00
README.md Modified readme & contributing. 2019-04-02 14:59:59 +02:00

README.md

KickC - Optimizing C-family Language Compiler for 6502

KickC is a compiler for a C-family language 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 crashes quite often resulting in cryptic errors. Also it will at times create 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 major breaking changes (to syntax, to semantics, etc.) may be implemented in the next versions.