From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15803 invoked by alias); 13 Jan 2004 00:23:08 -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 15768 invoked from network); 13 Jan 2004 00:23:07 -0000 Received: from unknown (HELO mail-out3.apple.com) (17.254.13.22) by sources.redhat.com with SMTP; 13 Jan 2004 00:23:07 -0000 Received: from mailgate2.apple.com (a17-128-100-204.apple.com [17.128.100.204]) by mail-out3.apple.com (8.12.10/8.12.9) with ESMTP id i0D0N7ou029864 for ; Mon, 12 Jan 2004 16:23:07 -0800 (PST) Received: from relay3.apple.com (relay3.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 4.3.6) with ESMTP id ; Mon, 12 Jan 2004 16:23:07 -0800 Received: from [17.201.24.57] (polskifiat.apple.com [17.201.24.57]) by relay3.apple.com (8.12.10/8.12.9) with ESMTP id i0D0N7IE022152; Tue, 13 Jan 2004 00:23:07 GMT In-Reply-To: <200401130118.27506.s.bosscher@student.tudelft.nl> References: <90200277-4301-11D8-BDBD-000A95B1F520@apple.com> <1073951351.3458.162.camel@minax.codesourcery.com> <02AF54EA-455D-11D8-B7FE-000393673036@apple.com> <200401130118.27506.s.bosscher@student.tudelft.nl> Mime-Version: 1.0 (Apple Message framework v609) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: Geoff Keating , Mark Mitchell , gcc@gcc.gnu.org, Phil Edwards From: Ziemowit Laski Subject: Re: gcc 3.5 integration branch proposal Date: Tue, 13 Jan 2004 00:23:00 -0000 To: Steven Bosscher X-SW-Source: 2004-01/txt/msg00753.txt.bz2 On 12 Jan, 2004, at 16.18, Steven Bosscher wrote: > On Tuesday 13 January 2004 01:11, Ziemowit Laski wrote: >> On 12 Jan, 2004, at 15.49, Mark Mitchell wrote: >>> Apple (and some other vendors, including CodeSourcery) is in the >>> position of doing its own release management and bug-fixing based on >>> various versions of GCC. Therefore, having high-quality FSF releases >>> may not make much of a difference to Apple; Apple doesn't use it >>> directly anyhow. >> >> And the reason we don't is because the FSF keeps shooting down our >> patches. >> You just can't have it both ways. > > And Apple keeps ignoring existing infrastructure. I understand the > inconvenience for you, but you should _fix_ patches, not force in. Please explain what you mean by 'infrastucture' and just how evil Apple is ignoring it. Also please explain how to fix patches that were shot down _on principle_, such as my recent AltiVec work. --Zem -------------------------------------------------------------- Ziemowit Laski 1 Infinite Loop, MS 301-2K Mac OS X Compiler Group Cupertino, CA USA 95014-2083 Apple Computer, Inc. +1.408.974.6229 Fax .5477