From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29943 invoked by alias); 7 May 2002 16:41:29 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 29928 invoked from network); 7 May 2002 16:41:27 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 7 May 2002 16:41:27 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 1F3653D2B; Tue, 7 May 2002 12:41:33 -0400 (EDT) Message-ID: <3CD803BC.5060900@cygnus.com> Date: Tue, 07 May 2002 09:41:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0rc1) Gecko/20020429 X-Accept-Language: en-us, en MIME-Version: 1.0 To: joern.rennecke@st.com Cc: aoliva@redhat.com, ezannoni@redhat.com, gcc@gcc.gnu.org, gdb@sources.redhat.com, bje@redhat.com Subject: Re: SH5 compact register numbering in gcc -> gdb interface References: <3CCED903.294513BE@st.com> <15568.36275.110744.510692@localhost.redhat.com> <3CD12BF8.7E1650C1@st.com> <3CD7EB51.7816DD1@st.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-05/txt/msg00050.txt.bz2 > > I was proposing only to change the SHcompact mapping, so that code > compiled with the default options won't be affected. Moreover, there > are still a number of bugs in gcc 3.1 that affect the SH5 port, some > of which can only be fixed with changes to the machine-independent sources. > I am working on this, but it is not feasible to finish this work in time > for gcc 3.1 . Hence, I'd expect some gcc 3.2 snapshots to be better > for SH5 than gcc 3.1 for production code. > > Another reason to switch to a post 3.1 compiler will be debugging speed. > The prologue-disassembling slows backtraces considerably when debugging > on real hardware. We are currently working on SH gcc emitting proper > cfi information, and gdb making use of it. For SH4 this has already > proved to make quite an improvement, and the gcc bug fixes for this > are among the next patches I intend to put into the FSF gcc repository. Humor me here. How do you use dwarf2 cfi to unwind a compact register (saved on the stack) back to a media register? In addition to the address of the saved register you'll need to know that only part of the register was saved. Does CFI describe this? Andrew