This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Re: about the interfaces of a front end
- From: "daizisheng" <daizi at ustc dot edu>
- To: "gcc" <gcc at gcc dot gnu dot org>
- Date: Wed, 28 Jan 2004 15:46:24 CST 0008
- Subject: Re: Re: about the interfaces of a front end
- Reply-to: daizi at ustc dot edu
Replyed From: daizisheng <daizi@ustc.edu>
> "daizisheng" <daizi@ustc.edu> writes:
>
> > i have finished my demo front end.
> > i found that a front end has to offer other things besides the
> > lang_hooks.
> > E.g:
> > convert(),
> > builtin_function(),
> > tree_code_type[],
> > tree_code_length[],
> > tree_code_name[].
> >
> > but why not put these datas in the lang_hooks structure?
>
> Because no one has moved them yet. Patches are welcome. (The
> tree_code_* arrays will require more care than the others.)
>
> > btw,when i built my front end,it ended with error
> > :no reference to gt_ggc_mx_lang_tree_node and gt_ggc_mx_language_function.
> > after i wrote them myself,i succeded.
> > what does that two functions mean??
>
> These are supposed to be generated automatically by the 'gengtype'
> program. See http://gcc.gnu.org/onlinedocs/gccint/Files.html for
> how to get it to do that.
i have read that several times,but i find little things.
i also have read the treelang front end.
i just find that:
these two functions of treelang are in gt-c-decl.h.
the file is generated from c-decl.c which is not part of the treelang front end.
so, if i do not include these c front end files in my front end,
what i should do??
>
> zw
>
--
USTC Alumni Email System