From: "Kei Sakamoto" <sakamoto.kei@renesas.com>
To: <gdb-patches@sources.redhat.com>
Subject: No set_gdbarch_* functions for hardware watchpoints
Date: Thu, 04 Mar 2004 09:34:00 -0000 [thread overview]
Message-ID: <012c01c401cc$40c9ce20$5169910a@E5A02646> (raw)
Hello,
I'm implementing hardware watchpoints for m32r target and
I found that there was no set_gdbarch_* functions for hardware
watchpoints.
I can use macros instead of set_gdbarch_* functions like other
targets, but it means m32r target becomes MULTI_ARCH_PARTIAL.
I don't think it's a good implementation.
Would anyone add set_gdbarch_* functions for hardware watchpoints?
===
Kei Sakamoto
Renesas Technology Corp.
sakamoto.kei@renesas.com
WARNING: multiple messages have this Message-ID
From: "Kei Sakamoto" <sakamoto.kei@renesas.com>
To: <gdb-patches@sources.redhat.com>
Subject: No set_gdbarch_* functions for hardware watchpoints
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <012c01c401cc$40c9ce20$5169910a@E5A02646> (raw)
Message-ID: <20040319000900.5kG-o2Nn2hcaVk-h5MqUUMaIZfgHCOX59NZCVdb0qO4@z> (raw)
Hello,
I'm implementing hardware watchpoints for m32r target and
I found that there was no set_gdbarch_* functions for hardware
watchpoints.
I can use macros instead of set_gdbarch_* functions like other
targets, but it means m32r target becomes MULTI_ARCH_PARTIAL.
I don't think it's a good implementation.
Would anyone add set_gdbarch_* functions for hardware watchpoints?
===
Kei Sakamoto
Renesas Technology Corp.
sakamoto.kei@renesas.com
next reply other threads:[~2004-03-04 9:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 9:34 Kei Sakamoto [this message]
2004-03-04 15:53 ` Andrew Cagney
2004-03-19 0:09 ` 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
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 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='012c01c401cc$40c9ce20$5169910a@E5A02646' \
--to=sakamoto.kei@renesas.com \
--cc=gdb-patches@sources.redhat.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