Quote:
- Tiny C Compiler by Fabrice Bellard at
http://bellard.org/tcc/tcc-doc.html - CC500 by Edmund Grimley-Evans at
http://homepage.ntlworld.com/edmund.gri ... ans/cc500/
- 8cc by Rui Ueyama at
https://github.com/rui314/8ccThose compilers seems to focus on completely different goals than produce small or fast code output.
This means that while those compilers have other qualities (be small, be fast, be educational), the produced code will be absolutely terrible, and definitely not fast or small, which is usually the goal that a programmer wants to achieve.
Quote:
because we already have cc65 for the 6502
The generated code is pretty terrible. You must declare all variables STATIC by hand if you want them to not use the horribly managed "software stack frame" of CC65.
The most interesting start point is probably [url="http://www.kdef.com/geek/vic/quetz.html"]that compiler with a incredible name starting in Q[/url].
However it wasn't updated for 8 years and is largely incomplete (for instance, array and pointer support is incomplete).
Quote:
Compared to gcc?
No, compared to other computer science related projects I've had to deal so far.
Quote:
I needed gcc for the ARM last year, and it wasn't available in precompiled form for my Linux distribution, so I had to compile it from source.
I did that too, in fact it's not that hard, but I agree it's crazy how bit it is. Thanks god you don't have to understand code to compile it. However you definitely have to understand most of it in order to contribute to it.