This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] New GDB target iq2000
- From: Corinna Vinschen <vinschen at redhat dot com>
- To: gdb-patches at sources dot redhat dot com
- Date: Tue, 8 Mar 2005 09:59:58 +0100
- Subject: Re: [RFA] New GDB target iq2000
- References: <20050222114141.GA18314@cygbert.vinschen.de> <20050307213534.GB28207@nevyn.them.org>
- Reply-to: gdb-patches at sources dot redhat dot com
On Mar 7 16:35, Daniel Jacobowitz wrote:
> On Tue, Feb 22, 2005 at 12:41:41PM +0100, Corinna Vinschen wrote:
> > Hi,
> >
> > this posting contributes the iq2000 code for GDB.
> >
> > There's just one problem with it. Older GCC code (older than two days,
> > actually), emits an asymmetrical register numbering in the dwarf2 debugging
> > output. The iq2000 uses register 31 as link register, which contains the
> > return address to the calling function. For some reason GCC emitted the
> > register number 26 in the dwarf2 information for this register. Every
> > other register has been used unchanged in dwarf2, so there was no
> > unambiguous translation from dwarf2 register numbers to real register
> > numbers, if the dwarf2 register was "26". This has been fixed yesterday
> > in GCC HEAD.
> >
> > As a result, the dwarf2 frame sniffer has a problem with code generated
> > by GCC's older than two days. This is no problem for the iq2000 frame
> > sniffer implemented in iq2000-tdep.c, but as usual, the iq2000 frame
> > sniffer is appended after the dwarf2 frame sniffer:
> >
> > frame_unwind_append_sniffer (gdbarch, dwarf2_frame_sniffer);
> > frame_unwind_append_sniffer (gdbarch, iq2000_frame_sniffer);
> >
> > Would that be a good reason to disable the dwarf2 frame sniffer for now?
> > Or shall I leave that as is?
>
> This is OK; I'll handle the linetable issues separately.
Thanks, applied.
Corinna
--
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat, Inc.