From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31923 invoked by alias); 19 Jan 2004 18:26:30 -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 31909 invoked from network); 19 Jan 2004 18:26:29 -0000 Received: from unknown (HELO mail.codesourcery.com) (65.74.133.9) by sources.redhat.com with SMTP; 19 Jan 2004 18:26:29 -0000 Received: (qmail 8488 invoked from network); 19 Jan 2004 18:26:18 -0000 Received: from taltos.codesourcery.com (zack@66.92.218.83) by mail.codesourcery.com with DES-CBC3-SHA encrypted SMTP; 19 Jan 2004 18:26:18 -0000 Received: by taltos.codesourcery.com (sSMTP sendmail emulation); Mon, 19 Jan 2004 10:26:18 -0800 From: "Zack Weinberg" To: kenner@vlsi1.ultra.nyu.edu (Richard Kenner) Cc: gcc@gcc.gnu.org Subject: Re: Can we speed up the gcc_target structure? References: <10401191820.AA00339@vlsi1.ultra.nyu.edu> Date: Mon, 19 Jan 2004 18:26:00 -0000 In-Reply-To: <10401191820.AA00339@vlsi1.ultra.nyu.edu> (Richard Kenner's message of "Mon, 19 Jan 04 13:20:32 EST") Message-ID: <87wu7npzg5.fsf@egil.codesourcery.com> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2004-01/txt/msg01339.txt.bz2 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