From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32074 invoked by alias); 5 Jul 2002 22:24:47 -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 32037 invoked from network); 5 Jul 2002 22:24:45 -0000 Received: from unknown (HELO desire.geoffk.org) (12.235.56.190) by sources.redhat.com with SMTP; 5 Jul 2002 22:24:45 -0000 Received: (from geoffk@localhost) by desire.geoffk.org (8.11.6/8.11.6) id g65MOUd23134; Fri, 5 Jul 2002 15:24:30 -0700 X-Authentication-Warning: desire.geoffk.org: geoffk set sender to geoffk@geoffk.org using -f To: David Edelsohn CC: gcc@gcc.gnu.org Subject: Re: C++ binary compatibility between GCC 3.1 and GCC 3.2? References: <200207052212.SAA21066@makai.watson.ibm.com> From: Geoff Keating Date: Fri, 05 Jul 2002 22:18:00 -0000 In-Reply-To: <200207052212.SAA21066@makai.watson.ibm.com> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-07/txt/msg00252.txt.bz2 David Edelsohn writes: > I thought that after GCC 3.1 was released, C++ bugs were suppose > to be fixed in a backward-compatible way not requiring incompatible > changes in the ABI, even if that required extra work. I don't believe that's possible in this case. Of the three bugs I've seen referenced, two are layout problems; there's no way to be compatible if GCC currently expects a field to be in one place and the ABI requires it to be in another, especially if the two places overlap. -- - Geoffrey Keating