From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25269 invoked by alias); 20 Jan 2004 18:52:28 -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 25245 invoked from network); 20 Jan 2004 18:52:22 -0000 Received: from unknown (HELO mail-out3.apple.com) (17.254.13.22) by sources.redhat.com with SMTP; 20 Jan 2004 18:52:22 -0000 Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225]) by mail-out3.apple.com (8.12.10/8.12.9) with ESMTP id i0KIqLnM003452 for ; Tue, 20 Jan 2004 10:52:21 -0800 (PST) Received: from relay3.apple.com (relay3.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.3.6) with ESMTP id ; Tue, 20 Jan 2004 10:52:21 -0800 Received: from [17.219.199.36] ([17.219.199.36]) by relay3.apple.com (8.12.10/8.12.9) with ESMTP id i0KIq6N7007495; Tue, 20 Jan 2004 18:52:06 GMT In-Reply-To: References: <90200277-4301-11D8-BDBD-000A95B1F520@apple.com> <200401192120.53057.ebotcazou@libertysurf.fr> <51C2CB76-4AC7-11D8-90DA-0030657EA24A@apple.com> <200401192304.01694.ebotcazou@libertysurf.fr> Mime-Version: 1.0 (Apple Message framework v609) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: Scott Robert Ladd , Robert Dewar , gcc@gcc.gnu.org, Nick Burrett , Eric Botcazou , Gabriel Dos Reis , Marc Espie From: Geoffrey Keating Subject: Re: gcc 3.5 integration branch proposal Date: Tue, 20 Jan 2004 18:52:00 -0000 To: Alexandre Oliva X-SW-Source: 2004-01/txt/msg01536.txt.bz2 On 19/01/2004, at 6:43 PM, Alexandre Oliva wrote: > On Jan 19, 2004, Geoff Keating wrote: > >> On Jan 19, 2004, at 2:04 PM, Eric Botcazou wrote: >>>> I would look at it this way: Why should a professional developer >>>> based >>>> in the US try to make GCC work on anything less than this machine? >>>> It's clearly not cost-effective to spend any significant time doing >>>> so. >>> >>> My point of view is exactly reverse :-) Why should a developer not >>> keep GCC >>> working on such a machine? > >> Because it's a waste of the developer's time? > > Err... And under what kind of logic is getting the compiler slower > not a waste of time for every GCC developer (that has to bootstrap and > test the whole thing for every patch) and user (that runs GCC to build > their own applications). I didn't say the developer should make GCC slower. I said the developer should not worry about performance on *old* machines. Performance on *new* machines is still a concern. They are often not the same thing.