10 Oct
2003
10 Oct
'03
7:20 a.m.
A number of C compilers on small architectures have solved this problem by
having 2, sometimes 4, distinct compiling phases, and passing data through
temporary files. This gives you a lot more leeway in code space. I've seen
preprocessor pass, tokenization pass, code generator pass, and in some cases,
the 4th pass is the assembler (which I generally prefer over
direct-to-assembly, since you can insert a user-written processing phase if
you want to get funky).
--John
On Friday 10 October 2003 14:14 pm, Jay West wrote:
I am looking for full source code for a *VERY* tiny C
compiler written in
any common assembly language. I'm much more concerned with size of the
compiler than functionality/features. Can anyone suggest one or know where
the source might by laying around? I thought I had heard ages ago about
some microcomputer C compilers being well under 32K.
As to how this relates to classiccmp... well.. *blush* I'm actually
thinking of porting C to the HP2100. The whole thing has to fit in 32K of
ram, including drivers, etc. Not sure what OS it will be placed on, perhaps
HP-IPL/OS. Might make a simple native OS for it or might even make it
standalone, not sure yet.
Did I recently post about being overcomitted? heh
Jay
---
[This E-mail scanned for viruses by Declude Virus]