From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10810 invoked by alias); 30 Aug 2004 10:19:45 -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 10796 invoked from network); 30 Aug 2004 10:19:42 -0000 Received: from unknown (HELO vlsi1.ultra.nyu.edu) (128.122.140.213) by sourceware.org with SMTP; 30 Aug 2004 10:19:42 -0000 Received: by vlsi1.ultra.nyu.edu (4.1/1.34) id AA24170; Mon, 30 Aug 04 06:22:33 EDT Date: Mon, 30 Aug 2004 10:44:00 -0000 From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner) Message-Id: <10408301022.AA24170@vlsi1.ultra.nyu.edu> To: neroden@fastmail.fm Subject: Re: GCC 3.5 Status (2004-08-29) Cc: gcc@gcc.gnu.org X-SW-Source: 2004-08/txt/msg01472.txt.bz2 I notice that the, uh, "project" to get Ada bootstrapping (Kenner, when can we expect this?) is not listed. These changes will presumably be accepted in stage 3? Because it's not a "project" in the sense of new development, but rather bugs that Ada triggers in middle-end code. Fixing bugs is Stage 3 work. So the timing of the Ada work is not relevent to entering Stage 3. However, I'm beginning to worry that Ada is going to delay the release of GCC 3.5 substantially if it's not bootstrapping soon, because the long period without Ada bootstrapping is likely to lead to bug discoveries when Ada is revived from the dead. Well it was bootstrapping on and off but indeed various changes have broken it for about two weeks. Part of the reason for the long period was that I was in Europe for a meeting for about a week. In any event, as of yesterday afternoon, I have it bootstrapping in my tree. It should be bootstrapping again in the GCC CVS in a day or so. It'll be more work to get it ACATS clean because some of the kludges I used to work around bugs will need to be converted into the proper fix. Is Ada functioning a requirement for the release? If so it seems a moderately bad idea to go into stage 3 with it totally busted. The answer to the first question has always been "no". But in practice, my expectation is that it will work fine on the release.