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: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: stevenb at suse dot de
- Cc: gcc at gcc dot gnu dot org
- Date: Sat, 5 Jun 04 13:22:42 EDT
- Subject: Re: BUILT_IN usage in tree-nested.c
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?
And isn't it tricky to figure out which of the ons used by the
middle-end are *really* going to be needed?