From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32011 invoked by alias); 4 Jul 2002 16:35:10 -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 31998 invoked from network); 4 Jul 2002 16:35:08 -0000 Received: from unknown (HELO Cantor.suse.de) (213.95.15.193) by sources.redhat.com with SMTP; 4 Jul 2002 16:35:08 -0000 Received: from Hermes.suse.de (Charybdis.suse.de [213.95.15.201]) by Cantor.suse.de (Postfix) with ESMTP id A5E2714CB3 for ; Thu, 4 Jul 2002 18:35:07 +0200 (MEST) Received: from aj by arthur.inka.de with local (Exim 3.34 #1) id 17Q9ZS-0005Mx-00 for gcc@gcc.gnu.org; Thu, 04 Jul 2002 18:35:06 +0200 To: gcc@gcc.gnu.org Subject: C++ binary compatibility between GCC 3.1 and GCC 3.2? From: Andreas Jaeger Date: Thu, 04 Jul 2002 09:55:00 -0000 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/msg00195.txt.bz2 Jason committed recently patch to fix a number of C++ Bugs in the ABI: http://gcc.gnu.org/ml/gcc-patches/2002-06/msg01275.html What does this mean for binary compatibility between GCC 3.1 and GCC 3.2? With the introduction of GCC 3 and its ABI, the expectation by users is that we won't have binary incompatible changes. Unfortunatly the - AFAIK valid - bug reports show that the ABI implemention was buggy and therefore needed to change. 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. Would it make sense for a distribution starting to ship GCC 3.1 to apply that bugfix? I prefer not to do this since it would mean that then two different GCC 3.1 release are binary incompatible :-(. But it would allow an easier upgrade to GCC 3.2 - or distributors are stuck with GCC 3.1 like some where stuck with GCC 2.95 due to the binary incompatibilities between 2.95, 3.0 and 3.1 which were known before. Andreas -- Andreas Jaeger SuSE Labs aj@suse.de private aj@arthur.inka.de http://www.suse.de/~aj