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: pinskia at physics dot uc dot edu
- Cc: gcc at gcc dot gnu dot org, rth at redhat dot com
- Date: Sat, 5 Jun 04 13:20:13 EDT
- Subject: Re: BUILT_IN usage in tree-nested.c
But Java does not need that one so it does not initializes it. That is
all. Since Java, I think, un-nests its functions/classes itself before
getting to
gimple does not need it at all.
Well, it's a confusing situation, at least.
gimplify.c references BUILT_IN_STACK_{SAVE,RESTORE},
BUILT_IN_MEMCPY, and BUILT_IN_PROFILE_{ENTER,EXIT}}; tree-mudflap.c
references BUILT_IN_STACK_ALLOC; tree-nested.c references
BUILT_IN_NONLOCAL_GOTO and BUILT_IN_{ADJUST,INIT}_TRAMPOLINE; and
tree-ssa-ccp.c references BUILT_IN_TRAP.
java/builtins.c defines *none* of those.
Where is it documented under what conditions front ends have to
initialize which builtins and how to do it?