From owner-freebsd-current Thu Aug 15 12:27:10 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF61337B400 for ; Thu, 15 Aug 2002 12:27:06 -0700 (PDT) Received: from h132-197-179-27.gte.com (h132-197-179-27.gte.com [132.197.179.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D5E343E86 for ; Thu, 15 Aug 2002 12:27:06 -0700 (PDT) (envelope-from ak03@gte.com) Received: from kanpc.gte.com (localhost [IPv6:::1]) by h132-197-179-27.gte.com (8.12.5/8.12.5) with ESMTP id g7FJR4Dg084892; Thu, 15 Aug 2002 15:27:04 -0400 (EDT) (envelope-from ak03@kanpc.gte.com) Received: (from ak03@localhost) by kanpc.gte.com (8.12.5/8.12.5/Submit) id g7FJR4cx084891; Thu, 15 Aug 2002 15:27:04 -0400 (EDT) Date: Thu, 15 Aug 2002 15:27:03 -0400 From: Alexander Kabaev To: "Long, Scott" Cc: Scott_Long@adaptec.com, jesse_gross@yahoo.com, current@freebsd.org Subject: Re: GCC 3.2 Message-Id: <20020815152703.2f0f23e1.ak03@gte.com> In-Reply-To: <2C7CBDC6EA58D6119E4A00065B3A24CB046493@btcexc01.btc.adaptec.com> References: <2C7CBDC6EA58D6119E4A00065B3A24CB046493@btcexc01.btc.adaptec.com> Organization: Verizon Data Services X-Mailer: Sylpheed version 0.8.1claws52 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I agree that gcc32 is not an ideal target either, but by going to it, > we can upgrade to gcc33 when it's available and not loose binary > compatibility (at least, according to the gcc folks). I'd rather > move to gcc32 right now and get the binary compatibility pain out of > the way, rather than wait for the last second to move to gcc33, > then have to delay FreeBSD 5.0 because everything in c++ land is > broken. The idea is to move to gcc 3.3-pre _now_ If GCC 3.2 has C++ ABI kinks worked out, GCC 3.3 surely has the same code in. GCC developers are trying to keep C++ ABI compatible between 3.2 and 3.3, but they are not giving any guaranrtees. -- Alexander Kabaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message