From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 15:23:18 2003 Return-Path: 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 93C2537B41D for ; Wed, 9 Jul 2003 15:23:15 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 030F543F85 for ; Wed, 9 Jul 2003 15:23:15 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.9/8.12.9) with ESMTP id h69MNDaQ029187 for ; Wed, 9 Jul 2003 15:23:14 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.9/8.12.9/Submit) id h69MNDFk029186 for current@FreeBSD.ORG; Wed, 9 Jul 2003 15:23:13 -0700 (PDT) Date: Wed, 9 Jul 2003 15:23:13 -0700 From: "David O'Brien" To: current@FreeBSD.ORG Message-ID: <20030709222313.GA29144@dragon.nuxi.com> Mail-Followup-To: David O'Brien References: <20030709170956.621dc901.ak03@gte.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030709170956.621dc901.ak03@gte.com> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.1-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Subject: Re: The upcoming GCC 3.3+ upgrade X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: current@FreeBSD.ORG List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2003 22:23:19 -0000 On Wed, Jul 09, 2003 at 05:09:56PM -0400, Alexander Kabaev wrote: > Unfortunately, importing a newer GCC means that we'll have yet another > ABI breakage on our hands. GCC 3.3 is more strict in C++ area and Just to be clear, there is no ABI breakage -- there is much more stricter adherence to standards (one might call it API breakage). There was a decicision by the GCC Steering Committee to not fix C++ ABI bugs between 3.2 and 3.3 by default. One can use the most bug-free(ahearance) to the C++ ABI standard using a commandline option. -- -- David (obrien@FreeBSD.org)