From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1081 invoked by alias); 1 Sep 2004 01:23:37 -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 1074 invoked from network); 1 Sep 2004 01:23:36 -0000 Received: from unknown (HELO nile.gnat.com) (205.232.38.5) by sourceware.org with SMTP; 1 Sep 2004 01:23:36 -0000 Received: from localhost (localhost [127.0.0.1]) by nile.gnat.com (Postfix) with ESMTP id 8EE32F2B8B; Tue, 31 Aug 2004 21:23:36 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 14343-01-2; Tue, 31 Aug 2004 21:23:36 -0400 (EDT) Received: from [127.0.0.1] (ppp3.gnat.com [205.232.38.213]) by nile.gnat.com (Postfix) with ESMTP id C4CA1F2A5F; Tue, 31 Aug 2004 21:23:33 -0400 (EDT) Message-ID: <4135249D.2020206@gnat.com> Date: Wed, 01 Sep 2004 01:23:00 -0000 From: Robert Dewar User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803 MIME-Version: 1.0 To: Florian Weimer Cc: Kai Henningsen , gcc@gcc.gnu.org Subject: Re: Ada policy References: <10408310328.AA02238@vlsi1.ultra.nyu.edu> <10408310328.AA02238@vlsi1.ultra.nyu.edu> <87acwc3qq6.fsf@codesourcery.com> <9FuB74S1w-B@khms.westfalen.de> <4134F84F.5080801@gnat.com> <87eklnuezm.fsf@deneb.enyo.de> In-Reply-To: <87eklnuezm.fsf@deneb.enyo.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at nile.gnat.com X-SW-Source: 2004-09/txt/msg00006.txt.bz2 Florian Weimer wrote: > * Robert Dewar: > > >>That's just not true. GNAT has been able to be built from 3.13 for >>many years (3.13 was released several years ago). We only introduce >>incompatibilities if we really need to for some significant cleanup >>or kludge removal. Earlier on that was more common, but we have not >>needed to do that for many years now. > > > I wonder why it's not possible to disable some aspects of -gnatg when > building the stage1 compiler. If there was such an option, you might > be able to do some cleanups (like instrumenting the code with more > precise pragmas to control warnings) without requiring newer compiler > versions to bootstrap. We can consider that sort of thing if we run into it, but as I noted, we can now bootstrap with very old versions of the compiler (3.13 was released in the middle of 2000, so over four years ago). I don't think there is any point at this stage in trying to make it work with older versions, and at the same time, we don't see any problems in maintaining the compatibility with 3.13 at least for now. If problems come up we can discuss them then. Meanwhile, I really think this is a non-issue. No one has ever had trouble from trying to use a too-old version of GNAT to bootstrap that we are aware of.