From: Paul Koning <paulkoning@comcast.net>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <palves@redhat.com>,
Andrew Burgess <andrew.burgess@embecosm.com>,
Craig Blackmore <craig.blackmore@embecosm.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] RISC-V: enable have_nonsteppable_watchpoint by default
Date: Mon, 08 Oct 2018 14:37:00 -0000 [thread overview]
Message-ID: <5019D845-3AEB-4287-A8BD-D9F96F5755B7@comcast.net> (raw)
In-Reply-To: <20181008142533.GA2993@adacore.com>
> On Oct 8, 2018, at 10:25 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>
>> [...] coupled with the fact that I'm not sure
>> whether there are in fact implementations of riscv that trigger
>> watchpoints after the write, makes me wonder, do we really need this?
>
> Actually - that's a very good point. Do we know of any architecture
> where the watchpoint triggers after the write?
I think MIPS is one. The documentation is not entirely clear but that's what I remember from using it.
paul
next prev parent reply other threads:[~2018-10-08 14:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 0:13 Craig Blackmore
2018-09-17 10:34 ` Andrew Burgess
2018-09-24 11:36 ` Craig Blackmore
2018-10-03 22:37 ` Joel Brobecker
2018-10-04 16:26 ` Craig Blackmore
2018-10-08 9:58 ` Andrew Burgess
2018-10-08 11:56 ` Pedro Alves
2018-10-08 14:25 ` Joel Brobecker
2018-10-08 14:37 ` Paul Koning [this message]
2018-10-08 14:42 ` Pedro Alves
2018-10-08 14:51 ` Joel Brobecker
2018-10-09 17:20 ` Craig Blackmore
2018-10-09 17:29 ` Paul Koning
2018-10-09 17:39 ` Pedro Alves
2018-10-23 10:34 ` Andrew Burgess
2018-10-08 14:50 ` Andreas Schwab
2018-09-17 12:54 ` Pedro Alves
2018-09-17 13:34 ` Andrew Burgess
2018-10-08 11:29 ` Pedro Alves
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=5019D845-3AEB-4287-A8BD-D9F96F5755B7@comcast.net \
--to=paulkoning@comcast.net \
--cc=andrew.burgess@embecosm.com \
--cc=brobecker@adacore.com \
--cc=craig.blackmore@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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