From: Daniel Jacobowitz <drow@false.org>
To: Kei Sakamoto <sakamoto.kei@renesas.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/m32r] Support hw watchpoint
Date: Tue, 09 Mar 2004 15:43:00 -0000 [thread overview]
Message-ID: <20040309154321.GA27765@nevyn.them.org> (raw)
Message-ID: <20040309154300.LOmovGgbS9X4wGs3Xofnm0aAU-0TleGMzhyQRueYJww@z> (raw)
In-Reply-To: <015401c40267$4b33f5c0$5169910a@E5A02646>
On Fri, Mar 05, 2004 at 01:06:53PM +0900, Kei Sakamoto wrote:
> Hello,
>
> The attached patch adds hardware watchpoint support to m32rsdi target,
> which is a remote target of m32r architecture.
> # Thank you for Andrew's suggestion.
>
> This patch is small because I've already implemented watchpoint functions
> in remote-m32r-sdi.c. I just didn't know how to define watchpoint's interface
> in multi-arch.
>
> OK to commit?
Yes, I think this is OK.
>
> Kei Sakamoto
> Renesas Technology Corp.
>
> ===
>
> 2004-03-05 Kei Sakamoto <sakamoto.kei@renesas.com>
>
> * remote-m32r-sdi.c: Support hardware watchpoint.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-03-09 15:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 9:34 No set_gdbarch_* functions for hardware watchpoints Kei Sakamoto
2004-03-04 15:53 ` Andrew Cagney
2004-03-19 0:09 ` [RFA/m32r] Support hw watchpoint Kei Sakamoto
2004-03-05 4:04 ` Kei Sakamoto
2004-03-19 0:09 ` Daniel Jacobowitz [this message]
2004-03-09 15:43 ` Daniel Jacobowitz
2004-03-10 0:27 ` Kei Sakamoto
2004-03-19 0:09 ` Kei Sakamoto
2004-03-19 0:09 ` No set_gdbarch_* functions for hardware watchpoints Andrew Cagney
2004-03-19 0:09 ` Kei Sakamoto
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=20040309154321.GA27765@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=sakamoto.kei@renesas.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