This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] callgraph and unit at time compilation
- From: Jan Hubicka <jh at suse dot cz>
- To: Diego Novillo <dnovillo at redhat dot com>
- Cc: Jan Hubicka <jh at suse dot cz>,"gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>,"gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Sat, 16 Nov 2002 10:11:19 +0100
- Subject: Re: [RFC] callgraph and unit at time compilation
- References: <20021116015332.GA22130@atrey.karlin.mff.cuni.cz> <1037413258.5015.19.camel@frodo>
> On Fri, 2002-11-15 at 20:53, Jan Hubicka wrote:
>
> > My question is whether this approach looks sensible. If so, I would
> > like to hear some comments from people more experienced with tree
> > inlining than I am.
> >
> I would strongly encourage you to approach this problem in a
> language-independent manner. In the future, we will want to do more
> than inlining. We need to be able to build flowgraph for all/several
> functions in one compilation unit so that we can do inter-procedural
> analyses and optimizations. We have some of the basic building blocks
> on the tree-ssa branch (there's even a call-graph builder).
>
> Solving this for only one front end will force us to solve the same
> problem for all the front ends. Better design something that we can use
> in the future to do real unit-at-a-time optimizations.
Yes, I would like to have this frontend independent, however at the
moment inlining it handles is frontend dependent. I tried to keep it
isolated as much as I can.
I will take a look at AST's callgraph builder shortly.
Honza
>
>
> Diego.