From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28620 invoked by alias); 18 Nov 2005 02:55:04 -0000 Received: (qmail 28563 invoked by uid 22791); 18 Nov 2005 02:55:03 -0000 Received: from dumbledore.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.11) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 18 Nov 2005 02:55:03 +0000 Received: (qmail 15805 invoked from network); 18 Nov 2005 02:55:01 -0000 Received: from unknown (HELO ?192.168.0.2?) (mitchell@127.0.0.2) by mail.codesourcery.com with ESMTPA; 18 Nov 2005 02:55:01 -0000 Message-ID: <437D427C.6060702@codesourcery.com> Date: Fri, 18 Nov 2005 02:55:00 -0000 From: Mark Mitchell User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) MIME-Version: 1.0 To: Andrew MacLeod CC: gcc mailing list Subject: Re: Register Allocation References: <1132246411.10098.153.camel@localhost.localdomain> In-Reply-To: <1132246411.10098.153.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 X-SW-Source: 2005-11/txt/msg00820.txt.bz2 Andrew MacLeod wrote: > It must be the season for this sort of thing :-) I have not yet read the entire document, but I would very much like to applaud both the goal of improving register allocation, and the spirit in which you've approached it: in particular, posting a design and getting comments before starting implementation. I'm glad to see that strategy taking hold as a general approach for major development initiatives. :-) -- Mark Mitchell CodeSourcery, LLC mark@codesourcery.com (916) 791-8304