From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 50579 invoked by alias); 8 Oct 2018 14:37:27 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 50565 invoked by uid 89); 8 Oct 2018 14:37:26 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: resqmta-po-01v.sys.comcast.net Received: from resqmta-po-01v.sys.comcast.net (HELO resqmta-po-01v.sys.comcast.net) (96.114.154.160) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 08 Oct 2018 14:37:25 +0000 Received: from resomta-po-12v.sys.comcast.net ([96.114.154.236]) by resqmta-po-01v.sys.comcast.net with ESMTP id 9UC8gfHuibeAp9Weyghbv2; Mon, 08 Oct 2018 14:37:24 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1539009444; bh=EEwS2PxkTMsgPWDSxvE6MMhm9IA/FfdeyYAbd/PVDgk=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=IQxpV5m9Iceq056mfk9su9iKe53XlAa6HXdgFhYbehR3HozNbYpviFxTJuYLZym1S 2/gRwV7yQD2YcCR6QFGSvHidvip0vgssHYvKLs2jy4Y0fSNVn0LKcLIusVBv5teulY zAsg712OVTD3Sd7G3LsiOu525uNTkj10eG9KiZUgJA4+qCdt6ZgPLM8aATVyJeesUn fByIBY9pG8rUmHhidKsVZiAc4JrPYQXTf1LsuWGw7jeBv3+Da4wbjio+jWOk0Sl4QL uIZQTrcZhUA/yMflshO4hm769UOXd56MxPsjVw3bZi96nKjf4l6sYz9Ruc++k2t3UD U0cC2r9WqaInQ== Received: from [192.168.10.125] ([73.60.223.101]) by resomta-po-12v.sys.comcast.net with ESMTPSA id 9WexgAv3Ujsr29WexgKqhY; Mon, 08 Oct 2018 14:37:24 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: [PATCH] RISC-V: enable have_nonsteppable_watchpoint by default From: Paul Koning In-Reply-To: <20181008142533.GA2993@adacore.com> Date: Mon, 08 Oct 2018 14:37:00 -0000 Cc: Pedro Alves , Andrew Burgess , Craig Blackmore , gdb-patches@sourceware.org Content-Transfer-Encoding: quoted-printable Message-Id: <5019D845-3AEB-4287-A8BD-D9F96F5755B7@comcast.net> References: <20180917103409.GJ5952@embecosm.com> <77978648-c391-0011-6c03-c7fd38429914@embecosm.com> <20181003223703.GA22933@adacore.com> <20181008095839.GC5952@embecosm.com> <4c4c1369-0f5c-549a-ed82-51563c5e6dd6@redhat.com> <20181008142533.GA2993@adacore.com> To: Joel Brobecker X-SW-Source: 2018-10/txt/msg00175.txt.bz2 > On Oct 8, 2018, at 10:25 AM, Joel Brobecker wrote: >=20 >> [...] 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? >=20 > 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 wh= at I remember from using it. paul