6502/kickc
1
0
Fork 0
mirror of https://gitlab.com/camelot/kickc.git synced 2024-11-07 23:07:29 +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,115 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%
ba9f99059a
Go to file
jespergravgaard ba9f99059a Added lexer support for all mnemonics used in CPU 65C02. Added Cpu65C02 instruction set.
2020-07-28 21:31:17 +02:00
.idea Now using kickassembler-5.16-65ce02 properly. 2020-07-26 02:25:33 +02:00
repo/cml/kickass/kickassembler Now using kickassembler-5.16-65ce02 properly. 2020-07-26 02:25:33 +02:00
src Added lexer support for all mnemonics used in CPU 65C02. Added Cpu65C02 instruction set. 2020-07-28 21:31:17 +02:00
.gitattributes Attempt at adding C-formatting. 2019-04-20 22:47:18 +02:00
.gitignore Added target files. 2020-05-11 11:04:32 +02:00
.gitlab-ci.yml Improved release script. Updated fragment cache file. 2020-06-14 13:49:20 +02:00
CONTRIBUTING.md
kickc.iml Now using kickassembler-5.16-65ce02 properly. 2020-07-26 02:25:33 +02:00
LICENSE.txt
NOTICE.txt
pom.xml Now using kickassembler-5.16-65ce02 properly. 2020-07-26 02:25:33 +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.