From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22455 invoked by alias); 4 Mar 2003 19:35:26 -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 22442 invoked from network); 4 Mar 2003 19:35:25 -0000 Received: from unknown (HELO egil.codesourcery.com) (66.92.14.122) by 172.16.49.205 with SMTP; 4 Mar 2003 19:35:25 -0000 Received: from zack by egil.codesourcery.com with local (Exim 3.36 #1 (Debian)) id 18qIC6-0006fg-00; Tue, 04 Mar 2003 11:35:18 -0800 To: Nathanael Nerode Cc: gcc@gcc.gnu.org Subject: Re: Target deprecation, round four From: Zack Weinberg Date: Tue, 04 Mar 2003 19:46:00 -0000 In-Reply-To: <20030304164917.GA358@doctormoo> (Nathanael Nerode's message of "Tue, 4 Mar 2003 11:49:17 -0500") Message-ID: <87znobylft.fsf@egil.codesourcery.com> User-Agent: Gnus/5.090016 (Oort Gnus v0.16) Emacs/21.2 References: <20030304164917.GA358@doctormoo> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-03/txt/msg00249.txt.bz2 Nathanael Nerode writes: >Richard Earnshaw said: >>Surely a release containing the deprecation announcement should be >>made *before* we start removing the code... As it stands you are >>proposing to delete the code from the mainline before most of the >>world is even aware of this. > > I deprecated vax-vms for 3.3 and promptly deleted it from mainline. > But this is because vax-vms (a) wasn't working, (b) hadn't been for > a long time, and (c) had over 10,000 lines of code devoted to it. I > would agree that deletions of *working* targets be delayed until the > version with the deprecation has been released. But deletions of > *non-working* targets, I think, can take place as soon as possible. The trouble with this otherwise reasonable suggestion is, (a) I have no way to tell whether the majority of the targets on the list are still working; (b) we have no schedule for the 3.3 release. Also, I am holding off on several performance patches that will involve touching lots of back-end code, because I don't want to waste time on targets that will be deleted in short order. And it's not hard to pull a deleted target back from CVS if someone does turn up expressing interest. But a wider announcement should happen. How about I send the list to gcc-announce now, and wait another week before making any actual changes? zw