Related articles |
---|
Intermediate compiler output format cdiggins@videotron.ca (christopher diggins) (2004-08-15) |
Re: Intermediate compiler output format cdc@maxnet.co.nz (Carl Cerecke) (2004-08-23) |
Re: Intermediate compiler output format kamalp@acm.org (2004-08-23) |
Re: Intermediate compiler output format nick.roberts@acm.org (Nick Roberts) (2004-08-23) |
Re: Intermediate compiler output format csy1032@nitc.ac.in (2004-08-23) |
Re: Intermediate compiler output format cdiggins@videotron.ca (christopher diggins) (2004-08-25) |
Re: Intermediate compiler output format cdiggins@videotron.ca (christopher diggins) (2004-08-25) |
From: | "christopher diggins" <cdiggins@videotron.ca> |
Newsgroups: | comp.compilers |
Date: | 25 Aug 2004 14:49:09 -0400 |
Organization: | Compilers Central |
References: | 04-08-100 04-08-107 |
Keywords: | tools, code, UNCOL |
Posted-Date: | 25 Aug 2004 14:49:09 EDT |
"Carl Cerecke" <cdc@maxnet.co.nz> wrote in message
> christopher diggins wrote:
> > I was wondering if there are any particularly well-known or
> > standardized formats for compilers that anyone could point me to.
>
> > Ideally the output format
> > should be type checked, platofrm independant and relatively easily
> > translated to languages like C or assembly.
>
> Sounds like C itself maybe an option as the output language.
The problem with C is that it is hard to retarget to another
destination like JVM or CLI. So what I want is the following:
Heron compiler -> XML
XML -> C
XML -> .NET bytecode
XML -> JVM bytecode
The goal is that the XML form can easily be parsed by others in order to
optimize, or re-target or analyze without having to hack the entire
compiler.
--
Christopher Diggins
http://www.heron-language.com
Return to the
comp.compilers page.
Search the
comp.compilers archives again.