Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: Use Dwarf 2 CFI on PowerPC targets
Date: Tue, 29 Mar 2005 17:42:00 -0000	[thread overview]
Message-ID: <vt2zmwm2vtv.fsf@zenia.home> (raw)
In-Reply-To: <je4qexj4zx.fsf@sykes.suse.de>

Andreas Schwab <schwab@suse.de> writes:

> Daniel Jacobowitz <drow@false.org> writes:
> 
> > On Wed, Sep 08, 2004 at 10:43:27AM -0500, Jim Blandy wrote:
> >> 
> >> This works fine on PowerPC E500 Linux; I'm still testing it on other
> >> platforms.  Thus it's a Request for Comments, not Approval.  I'll be
> >> back with test results on AIX, sim, and plain PowerPC Linux in a bit.
> >> 
> >> 2004-09-02  Jim Blandy  <jimb@redhat.com>
> >> 
> >> 	* rs6000-tdep.c: #include "dwarf2-frame.h".
> >> 	(rs6000_dwarf2_reg_to_regnum): Recognize 65 as another number for lr.
> >> 	(rs6000_gdbarch_init): Hook in dwarf2_frame_sniffer.
> >> 	* Makefile.in (rs6000-tdep.o): Update dependencies.
> >
> > Did you ever finish testing these?  There are now twelve targets which
> > use dwarf2_frame_sniffer and I've just posted a patch to enable it for
> > another, but PPC is still behind.
> 
> I've tested the patch with current HEAD on powerpc-suse-linux, and there
> are 73 regressions and 17 progressions.

Which GCC are you using?  One problem I ran into was that GCC's
.debug_frame information used one number for the return address
register in the CIE's, and a different one in the FDE's.


  reply	other threads:[~2005-03-29 17:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-08 15:44 Jim Blandy
2005-03-26 22:43 ` Daniel Jacobowitz
2005-03-27  0:40   ` Andreas Schwab
2005-03-29 17:42     ` Jim Blandy [this message]
2005-03-29 21:45       ` Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vt2zmwm2vtv.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=schwab@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox