From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12385 invoked by alias); 16 Sep 2003 03:10:50 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 12332 invoked from network); 16 Sep 2003 03:10:49 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 16 Sep 2003 03:10:49 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h8G3Al406730; Mon, 15 Sep 2003 23:10:48 -0400 Received: from post-office.corp.redhat.com (post-office.corp.redhat.com [172.16.52.227]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h8G3Aje03236; Mon, 15 Sep 2003 23:10:45 -0400 Received: from greed.delorie.com (dj.cipe.redhat.com [10.0.0.222]) by post-office.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h8G3Ahd27968; Mon, 15 Sep 2003 23:10:43 -0400 Received: (from dj@localhost) by greed.delorie.com (8.11.6/8.11.6) id h8G3AZ313629; Mon, 15 Sep 2003 23:10:35 -0400 Date: Tue, 16 Sep 2003 03:10:00 -0000 Message-Id: <200309160310.h8G3AZ313629@greed.delorie.com> From: DJ Delorie To: ac131313@redhat.com CC: drow@mvista.com, gdb-patches@sources.redhat.com, binutils@sources.redhat.com, gcc-patches@gcc.gnu.org In-reply-to: <3F667C15.50203@redhat.com> (message from Andrew Cagney on Mon, 15 Sep 2003 22:57:25 -0400) Subject: Re: [libiberty and gdb] floatformat_is_valid References: <20030915143933.GA22129@nevyn.them.org> <3F6626F9.90003@redhat.com> <20030915205815.GA4563@nevyn.them.org> <3F667C15.50203@redhat.com> X-SW-Source: 2003-09/txt/msg00354.txt.bz2 > There didn't seem to be a problem when "name" was added, or arm_ext > was deleted. Structures can be extended iff such extensions don't cause compatibility problems. Adding a member to a structure allocated by the application is bad; the sizes won't match. Adding one to a structure that's created only by libiberty itself is safer, providing the compatibility issues are understood.