This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: BUILT_IN usage in tree-nested.c
- From: Steven Bosscher <stevenb at suse dot de>
- To: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Cc: gcc at gcc dot gnu dot org
- Date: Sat, 5 Jun 2004 20:17:46 +0200
- Subject: Re: BUILT_IN usage in tree-nested.c
- Organization: SUSE Labs
- References: <10406051722.AA24044@vlsi1.ultra.nyu.edu>
On Saturday 05 June 2004 19:22, Richard Kenner wrote:
> Why would Java need trampolines, isn't that only needed if
> you have nested functions?
>
> You'd think so.
>
> But what about the rest I listed that are used in the middle-end and not
> defined by the Java front end?
>
> Isn't it redundant for each front end to have to refine all the builtins?
Yes :)
> And isn't it tricky to figure out which of the ons used by the
> middle-end are *really* going to be needed?
Yes, but what is wrong with defining all the builtins that the
middle-end _may_ need? I think the only requirement should be
that the builtin must be language independent. Things like
builtin_expect, the trampolines, etc. should all be defined in
a language independent part of the compiler.
Gr.
Steven