From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14948 invoked by alias); 6 Jul 2002 10:42:44 -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 14941 invoked from network); 6 Jul 2002 10:42:41 -0000 Received: from unknown (HELO maroon.csi.cam.ac.uk) (131.111.8.2) by sources.redhat.com with SMTP; 6 Jul 2002 10:42:41 -0000 Received: from student.cusu.cam.ac.uk ([131.111.179.82] helo=kern.srcf.societies.cam.ac.uk ident=mail) by maroon.csi.cam.ac.uk with esmtp (Exim 4.05) id 17Qn1U-0007zK-00; Sat, 06 Jul 2002 11:42:40 +0100 Received: from jsm28 (helo=localhost) by kern.srcf.societies.cam.ac.uk with local-esmtp (Exim 3.12 #1 (Debian)) id 17Qn1U-0003Qw-00; Sat, 06 Jul 2002 11:42:40 +0100 Date: Sat, 06 Jul 2002 05:40:00 -0000 From: "Joseph S. Myers" X-X-Sender: To: Andreas Jaeger cc: Subject: Re: C++ binary compatibility between GCC 3.1 and GCC 3.2? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-07/txt/msg00260.txt.bz2 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? Is libstdc++ yet ready to be binary compatible between successive major releases? If not, how useful is binary compatibility of the underlying C++ ABI? -- Joseph S. Myers jsm28@cam.ac.uk