Re: Third party compiler middle and back-end

glen herrmannsfeldt <gah@ugcs.caltech.edu>
Sun, 10 Oct 2010 05:01:27 +0000 (UTC)

          From comp.compilers

Related articles
Third party compiler middle and back-end danielzazula@gmail.com (Daniel Zazula) (2010-10-08)
Re: Third party compiler middle and back-end gah@ugcs.caltech.edu (glen herrmannsfeldt) (2010-10-10)
Re: Third party compiler middle and back-end usenet@vfx.org.uk (Mike Playle) (2010-10-10)
Re: Third party compiler middle and back-end redbrain@gcc.gnu.org (Philip Herron) (2010-10-10)
Re: Third party compiler middle and back-end cr88192@hotmail.com (BGB / cr88192) (2010-10-10)
Re: Third party compiler middle and back-end jm@bourguet.org (Jean-Marc Bourguet) (2010-10-11)
Re: Third party compiler middle and back-end j.o.williams.jow@gmail.com (James O. Williams) (2010-10-11)
Re: Third party compiler middle and back-end gneuner2@comcast.net (George Neuner) (2010-10-12)
[13 later articles]
| List of all articles for this month |

From: glen herrmannsfeldt <gah@ugcs.caltech.edu>
Newsgroups: comp.compilers
Date: Sun, 10 Oct 2010 05:01:27 +0000 (UTC)
Organization: Aioe.org NNTP Server
References: 10-10-010
Keywords: code, tools
Posted-Date: 11 Oct 2010 00:33:09 EDT

Daniel Zazula <danielzazula@gmail.com> wrote:


> 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.


It is a little unusual to try writing a compiler without knowing
a reasonable amount about the instruction set of the processor,
but I suppose it is possible.


Note that "assembly language" sometimes means the hardware
instructions in symbolic form, and other times the assembler
input including non-code-generating assembler instructions.


> So I though about using a third party back-end, I would write the
> front-end that parse the language into a intermediate code and leave
> the rest to the back-end. I gave a look at GCC but it is too big, too
> vast and too complex for what I want. Microsoft's Phoenix also don't
> work for me since it generates CIL.


To me, the LCC back end is much more readable. Then again,
that could just be me.


(snip)


-- glen



Post a followup to this message

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