Related articles |
---|
standard intermediate representation for C/C++ ? martin@CS.UCLA.EDU (1992-04-30) |
Re: standard intermediate representation for C/C++ ? macrakis@osf.org (1992-05-05) |
Re: standard intermediate representation for C/C++ ? martin@CS.UCLA.EDU (1992-05-07) |
Re: standard intermediate representation for C/C++ ? sdm@cs.brown.edu (1992-05-08) |
Re: standard intermediate representation for C/C++ ? root@grok19.columbiasc.NCR.COM (Dave Howell) (1992-05-11) |
Re: standard intermediate representation for C/C++ ? dalamb@qucis.queensu.ca (1992-05-13) |
Re: standard intermediate representation for C/C++ ? rascal@verdix.com (1992-05-14) |
Re: standard intermediate representation for C/C++ ? bevan@computer-science.manchester.ac.uk (Stephen J Bevan) (1992-05-15) |
[4 later articles] |
Newsgroups: | comp.lang.c,comp.lang.c++,comp.compilers |
From: | macrakis@osf.org (Stavros Macrakis) |
Keywords: | C, C++ |
Organization: | OSF Research Institute |
References: | 92-05-010 |
Date: | Tue, 5 May 1992 17:12:35 GMT |
martin@CS.UCLA.EDU (david l. martin) writes:
[Re] intermediate representation for ANSI C?... the sort of information
which a compiler front-end passes to the back-end. [Useful for] compiler
builders, or tools in an integrated environment [e.g.] DIANA.
John comments:
[...The RTL used in GCC is fairly well documented...]
RTL does not solve David Martin's tool problem, since it doesn't preserve
source information. Martin's question assumes that front ends pass tagged
syntax trees to back ends, but most compilers use lower-level
representations.
In fact, although Diana is great for source-level tools, it may not be the
most efficient way to compile Ada.
-s
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.