From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30112 invoked by alias); 6 Jul 2002 13:40:24 -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 30071 invoked from network); 6 Jul 2002 13:40:22 -0000 Received: from unknown (HELO Cantor.suse.de) (213.95.15.193) by sources.redhat.com with SMTP; 6 Jul 2002 13:40:22 -0000 Received: from Hermes.suse.de (Charybdis.suse.de [213.95.15.201]) by Cantor.suse.de (Postfix) with ESMTP id 4900E14489; Sat, 6 Jul 2002 15:40:21 +0200 (MEST) Received: from aj by arthur.inka.de with local (Exim 3.34 #1) id 17Qpjb-0006C7-00; Sat, 06 Jul 2002 15:36:23 +0200 Mail-Copies-To: never To: Gabriel Dos Reis Cc: "Joseph S. Myers" , Subject: Re: C++ binary compatibility between GCC 3.1 and GCC 3.2? References: From: Andreas Jaeger Date: Sat, 06 Jul 2002 07:49:00 -0000 In-Reply-To: (Gabriel Dos Reis's message of "06 Jul 2002 14:36:18 +0200") Message-ID: User-Agent: Gnus/5.090007 (Oort Gnus v0.07) XEmacs/21.4 (Artificial Intelligence, i386-suse-linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-07/txt/msg00270.txt.bz2 Gabriel Dos Reis writes: > "Joseph S. Myers" writes: > > | On Thu, 4 Jul 2002, Andreas Jaeger wrote: > | > | > What will this mean for distributions and for production usage of GCC > | > 3.1? I fear this means that folks cannot easily upgrade from GCC 3.1 > | > to GCC 3.2 since C++ is incompatible and all C++ libraries that are > | > needed for development need to be relinked. > | > | Where does libstdc++ fit into this? > > The library is not covered by the ABI requirement; but we try hard to > retain ABI compatibility. With symbol versioning (that is implemented in libstdc++) it shouldn't be a problem to retain ABI compatibility as long as the C++ ABI is stable. Andreas -- Andreas Jaeger SuSE Labs aj@suse.de private aj@arthur.inka.de http://www.suse.de/~aj