This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: build tree nodes vs expand as you go
- To: Fergus Henderson <fjh at cs dot mu dot oz dot au>
- Subject: Re: build tree nodes vs expand as you go
- From: Richard Henderson <rth at redhat dot com>
- Date: Fri, 22 Dec 2000 10:16:49 -0800
- Cc: gcc at gcc dot gnu dot org
- References: <20001221192159.A9474@hg.cs.mu.oz.au>
On Thu, Dec 21, 2000 at 07:21:59PM +1100, Fergus Henderson wrote:
> I'm trying to decide whether to build a gcc tree node for each
> statement in my source language (like e.g. the Java front-end does),
> or whether to just expand them directly, using expand_start_cond(),
> expand_else(), expand_end_cond() etc.
>
> What are the trade-offs here?
The long term vision is that a front end doesn't deal with rtl at all, but
instead hands off a tree describing the entire function to the middle end.
At which point we do tree-based optimizations, then convert to an oft
wished for mid-level rtl (more regular and less machine specific) and do
SSA based optimizations, then convert to the rtl used today.
So please do generate trees for the entire function.
r~