This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
RE: BookE/E500 support
- From: Kris Warkentin <KEWarken at qnx dot com>
- To: 'Daniel Jacobowitz' <drow at false dot org>, Andrew Cagney <cagney at gnu dot org>
- Cc: Kumar Gala <kumar dot gala at freescale dot com>, GDB <gdb at sources dot redhat dot com>
- Date: Tue, 19 Jul 2005 13:50:38 -0400
- Subject: RE: BookE/E500 support
Well there's definitely something strange going on then. There seems to be
a lot of e500 functionality in mainline/6.3. Does that mean someone is
going to have to go through it and figure out what made it in from the
branch and what still needs to be added?
This is why I was so confused. I couldn't find any reference to a merge but
there was a lot of code in there that looked like it was from the branch.
cheers,
Kris
-----Original Message-----
From: gdb-owner@sources.redhat.com
[mailto:gdb-owner@sources.redhat.com]On Behalf Of Daniel Jacobowitz
Sent: Tuesday, July 19, 2005 11:34 AM
To: Andrew Cagney
Cc: Kumar Gala; GDB
Subject: Re: BookE/E500 support
On Tue, Jul 19, 2005 at 11:27:59AM -0400, Andrew Cagney wrote:
> Kumar,
>
> The branch looks dead (there's been nothing on the list to suggest
> further merging effort).
>
> As for DW_OP_piece, I independantly added DW_OP_piece read support to
> GDB's mainline (it can't write though). That part proved to be
> relatively trivial and provides the more critical functionality.
Except, that patch hasn't been reviewed yet as far as I know. It's
still pending.
--
Daniel Jacobowitz
CodeSourcery, LLC