From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9100 invoked by alias); 25 May 2005 12:48:00 -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 9063 invoked by uid 22791); 25 May 2005 12:47:52 -0000 Received: from ns.suse.de (HELO mx1.suse.de) (195.135.220.2) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 25 May 2005 12:47:52 +0000 Received: from hermes.suse.de (hermes-ext.suse.de [195.135.221.8]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mx1.suse.de (Postfix) with ESMTP id C4241E82E; Wed, 25 May 2005 14:47:50 +0200 (CEST) Message-ID: <42947407.2080104@suse.de> Date: Wed, 25 May 2005 13:53:00 -0000 From: Paolo Carlini User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414 MIME-Version: 1.0 To: Theodore.Papadopoulo@sophia.inria.fr Cc: Daniel Jacobowitz , Zack Weinberg , Gabriel Dos Reis , gcc@gcc.gnu.org, jason@redhat.com, mark@codesourcery.com, dberlin@dberlin.org Subject: Re: libstdc++ soname and versioning References: <1116907280.9577.31.camel@localhost.localdomain> <20050524035919.GA23335@nevyn.them.org> <87fywdkvmp.fsf@codesourcery.com> <20050524134120.GA1680@nevyn.them.org> <1116976827.8637.25.camel@localhost.localdomain> <4293BC92.3090404@suse.de> <1116980082.8798.8.camel@localhost.localdomain> <20050525001108.GA21632@nevyn.them.org> <1116981148.8798.11.camel@localhost.localdomain> <20050525014728.GA23626@nevyn.them.org> <42943932.6020800@suse.de> <1117024851.22250.71.camel@mururoa> In-Reply-To: <1117024851.22250.71.camel@mururoa> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2005-05/txt/msg01364.txt.bz2 Theodore Papadopoulo wrote: >The real problem I think is not really casting an ABI in stone, but >merely to have "some stability" over time. Maybe the only thing that is >missing is a "commitment" of the C++ library ABI stable over a few (two, >three ?) major gcc releases as there is one for the core compiler (and >remember it took several releases to achieve it)... > > Just a quick comment: this is *already* happening, no doubts. We have v6 since 3.4.0... Paolo.