Related articles |
---|
Gnu C compiler RTL question dadorran@my-dejanews.com (1998-09-13) |
Re: Gnu C compiler RTL question kong@ece.ucdavis.edu (Timothy Kong) (1998-09-18) |
Re: Gnu C compiler RTL question lehotsky@tiac.net (1998-09-18) |
Re: Gnu C compiler RTL question misar@rbg.informatik.tu-darmstadt.de (1998-09-18) |
From: | misar@rbg.informatik.tu-darmstadt.de (Walter Misar) |
Newsgroups: | comp.compilers |
Date: | 18 Sep 1998 23:15:37 -0400 |
Organization: | main(){int i;for(i=0;i<3;i++)putchar(84+i*(10-9*i));} |
References: | 98-09-034 |
Keywords: | GCC, question |
dadorran@my-dejanews.com writes:
|> I read somewhere that the RTL is independent of the machine description, but
|> looking at some compiled code shows that it does depend on the registers used
|> as the stack and frame pointers.
|>
|> Are thes the only instances where this occurs??
No, while the RTL language is independant of the machine description, RTL code
heavily depends on it.
From the "Using and Porting GNU CC" document:
> People frequently have the idea of using RTL stored as text in a file as an
> interface between a language front end and the bulk of
> GNU CC. This idea is not feasible.
>
> GNU CC was designed to use RTL internally only. Correct RTL for a given
> program is very dependent on the particular target
> machine. And the RTL does not contain all the information about the program.
>
> The proper way to interface GNU CC to a new language front end is with
> the "tree" data structure. There is no manual for this data
> structure, but it is described in the files `tree.h' and `tree.def'.
( see http://www.student.informatik.tu-darmstadt.de/public/info/gcc/gcc_17.html#SEC148)
--
Walter Misar misar@rbg.informatik.tu-darmstadt.de
misar@hrz.tu-darmstadt.de
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.