This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: about the interfaces of a front end
- From: "Zack Weinberg" <zack at codesourcery dot com>
- To: daizi at ustc dot edu
- Cc: "gcc" <gcc at gcc dot gnu dot org>
- Date: Tue, 27 Jan 2004 23:11:15 -0800
- Subject: Re: about the interfaces of a front end
- References: <0061dfbc4e5b388e551d5a71a3788101@magicmail>
"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.
zw