From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6562 invoked by alias); 19 Jan 2004 19:05:12 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 6548 invoked from network); 19 Jan 2004 19:05:11 -0000 Received: from unknown (HELO vlsi1.ultra.nyu.edu) (128.122.140.213) by sources.redhat.com with SMTP; 19 Jan 2004 19:05:11 -0000 Received: by vlsi1.ultra.nyu.edu (4.1/1.34) id AA00753; Mon, 19 Jan 04 14:07:25 EST Date: Mon, 19 Jan 2004 19:05:00 -0000 From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner) Message-Id: <10401191907.AA00753@vlsi1.ultra.nyu.edu> To: zack@codesourcery.com Subject: Re: Can we speed up the gcc_target structure? Cc: gcc@gcc.gnu.org X-SW-Source: 2004-01/txt/msg01350.txt.bz2 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. True for some, but not others. Yes, we have a lot of macros which are actually functions, but we also have a lot of macros that are just a half dozen tokens which would have to be converted into a function.