This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Can we speed up the gcc_target structure?
- From: "Zack Weinberg" <zack at codesourcery dot com>
- To: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 19 Jan 2004 10:26:18 -0800
- Subject: Re: Can we speed up the gcc_target structure?
- References: <10401191820.AA00339@vlsi1.ultra.nyu.edu>
kenner@vlsi1.ultra.nyu.edu (Richard Kenner) writes:
> Does your opinion change if the target parameters are properly
> redesigned, as I suggested in another message to this thread?
>
> Somewhat, but I still wonder whether the complexity of such a scheme
> is worth the ability to have common .o files.
If done right, it ought to be simpler than target macros. If you look
at individual target macros in isolation, conversion from macro to
hook invariably makes the back-end interface simpler, just because it
forces you not to do the horrible define-here-redefine-there mess that
is the current state of a lot of the macros. So I think doing it
right will be natural, except where actual design effort is required,
such as for the calling-convention macros. And there the design
effort is worth it in its own terms.
zw