Re: Third party compiler middle and back-end

"Daniel Zazula" <danielzazula@gmail.com> wrote in message
>I want to write a compiler that generates assembly, but I do not know
> assembly, I've already started studying the FASM, but it will take
> much time to learn everything I need to know in order to write a
> decent back-end.
....snip...


Are you familiar with (T)he (A)msterdam (C)ompiler (K)it?
http://tack.sourceforge.net/


The project supports different front-ends and back-ends through a
common set of 'near-assembly-language' pseudo-ops. You can write your
own front-end to produce the same pseudo-ops, and use the existing x86
back-end to produce assembly language. The back-end also handles a
certain amount of optimization, as well. The techniques in TACK's
tools are not the latest-and-greatest, but they do work.


You might also look into the tools used in 'Retargetable Concurrent
Small C' from Dr. Dobb's. Small C is written in (a variant of) C
using recursive descent. You may be able to make a compatible front
in C by hand, or by using a tool like RDP -
http://www.cs.rhul.ac.uk/research/languages/projects/rdp.html. While
Retargetable CSC does not have an explicit x86 back-end, The code in
the SmallC 2.2 sources should give enough guidance to allow you make
the necessary adaptations for the M4 macros, etc.

Return to the comp.compilers page.
Search the comp.compilers archives again.