From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4935 invoked by alias); 10 Nov 2005 01:22:46 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 4919 invoked by uid 22791); 10 Nov 2005 01:22:44 -0000 Received: from ip127.bb146.pacific.net.hk (HELO stl.com.hk) (202.64.146.127) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 10 Nov 2005 01:22:44 +0000 Received: from rccomp.stl.com.hk ([192.168.100.200]) by stl.com.hk with esmtp (Exim 4.50) id 1Ea16e-000401-M6; Thu, 10 Nov 2005 09:20:00 +0800 Message-ID: <4372A0E9.9010801@tausq.org> Date: Thu, 10 Nov 2005 01:32:00 -0000 From: Randolph Chung User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050805) MIME-Version: 1.0 To: Joel Brobecker CC: gdb-patches@sources.redhat.com Subject: Re: [hppa] FYI: confusion in unwind descriptor field meaning References: <20051109203108.GX1635@adacore.com> <43728C6E.5010206@tausq.org> <20051110001750.GB1635@adacore.com> In-Reply-To: <20051110001750.GB1635@adacore.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2005-11/txt/msg00121.txt.bz2 Joel Brobecker wrote: >>Be careful here, some of this is to work around gcc's interpretation of >>these fields, which does not always correspond to the documentation. gcc >>only uses a few of the bits in the unwind record. > > Grumble. > > Yes, I know. It's the reason why I never got around to submit the few > changes we made locally. Our GCC has some local changes that make the > unwind descriptor more compatible between the two models. I am still > asking the details to the hppa specialist at AdaCore, but it seems > that starting with GCC 3.4, the frame was setup in a more compatible > way already. If you're interested, I'll let you know the details of > our implementation. Well, I think we need to work with upstream gcc. I know Dave has done some work to improve this with more recent versions of gcc. Let's try to document all the variations of compilers we claim to work with (gcc-3.x, gcc-4.x, HP aCC, etc) and we'll try to come up with something that works "everywhere". randolph -- Randolph Chung Debian GNU/Linux Developer, hppa/ia64 ports http://www.tausq.org/