Re: Tree inlining for the C front end (part 1 of 3)

[Richard Henderson <rth at redhat dot com>]

On Fri, Oct 05, 2001 at 03:30:31AM -0300, Alexandre Oliva wrote:
> I ended up keeping the macros in tree-inline.h because I found
> something like:
> 
> (lang_hooks.tree_inlining.a_relatively_long_name
>  ? (*lang_hooks.tree_inlining.a_relatively_long_name)(args)
>  : 0)
> 
> quite ugly.

So enforce a non-null value for the function.  You should not
worry about perceived overhead of the dummy call.  This isn't
even remotely on the critical path.

> For example, where would this function be declared, so that
> langhooks.h could refer to it? 

In langhooks.h.  I think it is a mistake that the default functions 
for target-def.h aren't all declared in target-def.h.

> And where would it be defined, so that all languages to which it applies
> get it? 

Well, it's tree inlining related, so how about tree-inline.c?


r~