From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] [1/4] SPU overlay support: New gdbarch_overlay_update routine
Date: Thu, 10 May 2007 21:55:00 -0000 [thread overview]
Message-ID: <20070510215528.GD3187@caradoc.them.org> (raw)
In-Reply-To: <200705072224.l47MOhOw023285@d12av02.megacenter.de.ibm.com>
On Tue, May 08, 2007 at 12:24:43AM +0200, Ulrich Weigand wrote:
> According to the overlays.exp test case, only the (obsolete) d10v
> and m32r targets support overlays. Thus I've installed the
> existing "simple" overlay manager for the m32r target only.
> If this is incorrect, it could be added to other targets as
> well. Or should we have the gdbarch function default always
> to simple_overlay_update?
I think it's fine the way you did it. Modulo the comments I just sent
out, this all looks fine (but NEWS-worthy).
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-05-10 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 22:24 Ulrich Weigand
2007-05-10 21:55 ` Daniel Jacobowitz [this message]
2007-05-10 22:28 ` Ulrich Weigand
2007-05-11 20:25 ` Ulrich Weigand
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=20070510215528.GD3187@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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