From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1984 invoked by alias); 19 Jan 2004 23:42:40 -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 1933 invoked from network); 19 Jan 2004 23:42:37 -0000 Received: from unknown (HELO vlsi1.ultra.nyu.edu) (128.122.140.213) by sources.redhat.com with SMTP; 19 Jan 2004 23:42:37 -0000 Received: by vlsi1.ultra.nyu.edu (4.1/1.34) id AA03475; Mon, 19 Jan 04 18:44:51 EST Date: Mon, 19 Jan 2004 23:42:00 -0000 From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner) Message-Id: <10401192344.AA03475@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/msg01410.txt.bz2 Whether by accident or intention you picked a lot of stuff having to do with register classes, Accident: I was going sequentially through alpha.h. Wasn't Michael Matz just saying that regclass.c needed a major rework anyway, or the new register allocator would never be able to replace the old? I don't know what his design looks like, or even if he has one yet, but surely there is a simpler way to structure this, that doesn't involve lots of little tiny macros. I don't see what that has to do with the specification of classes, which are attributes of the machine. Those macros are used by far more than just regclass.c and the register allocator ...