From: Daniel Jacobowitz <drow@false.org>
To: Greg Page <gpage@ind.alcatel.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Patch for GDB rs6000-tdep.c
Date: Wed, 17 May 2006 19:03:00 -0000 [thread overview]
Message-ID: <20060517183610.GA11377@nevyn.them.org> (raw)
In-Reply-To: <446B64BA.8050905@ind.alcatel.com>
On Wed, May 17, 2006 at 12:00:26PM -0600, Greg Page wrote:
> The attached is a patch for the file gdb-6.4/gdb/rs6000-tdep.c.
>
> The problem: The register definitions for the e500 assume only 4 bytes
> per floating-point register but the gdbserver assumes 8 bytes per
> floating-point register.
Gdbserver in the FSF tree doesn't have any concept of the e500
registers. This isn't the only thing that isn't going to work.
The right solution is to make GDB detect when it is talking to a
gdbserver that supports e500, and have the two negotiate how big
registers actually are. We're working on this, but it's complex.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-05-17 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 18:13 Greg Page
2006-05-17 19:03 ` Daniel Jacobowitz [this message]
[not found] ` <446B72FE.1070505@ind.alcatel.com>
2006-05-17 19:07 ` Daniel Jacobowitz
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=20060517183610.GA11377@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=gpage@ind.alcatel.com \
/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