From: Kris Warkentin <KEWarken@qnx.com>
To: 'Daniel Jacobowitz' <drow@false.org>, Andrew Cagney <cagney@gnu.org>
Cc: Kumar Gala <kumar.gala@freescale.com>, GDB <gdb@sources.redhat.com>
Subject: RE: BookE/E500 support
Date: Tue, 19 Jul 2005 17:51:00 -0000 [thread overview]
Message-ID: <1578FF984ABAD411AFA5000102C4BB5B0F064938@NIMBUS> (raw)
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
next reply other threads:[~2005-07-19 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 17:51 Kris Warkentin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-18 19:28 Kris Warkentin
2005-07-18 21:21 ` Kumar Gala
2005-07-19 15:27 ` Andrew Cagney
2005-07-19 15:33 ` 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=1578FF984ABAD411AFA5000102C4BB5B0F064938@NIMBUS \
--to=kewarken@qnx.com \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=kumar.gala@freescale.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).