Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jan.kratochvil@redhat.com, qiyaoltc@gmail.com,
	gdb-patches@sourceware.org
Subject: Re: ping: [patch] aarch64: PR 19806: watchpoints: false negatives + PR 20207 contiguous ones
Date: Fri, 20 Apr 2018 15:59:00 -0000	[thread overview]
Message-ID: <8d4d9262-305c-eb71-8752-80d729e0cc6a@redhat.com> (raw)
In-Reply-To: <83po2tyiu0.fsf@gnu.org>

On 04/20/2018 04:54 PM, Eli Zaretskii wrote:

>> diff --git a/gdb/NEWS b/gdb/NEWS
>> index 25c404bfc37..38043c4ff2e 100644
>> --- a/gdb/NEWS
>> +++ b/gdb/NEWS
>> @@ -35,6 +35,16 @@ SH-5/SH64 ELF			sh64-*-elf*, SH-5/SH64 support in sh*
>>  SH-5/SH64 running GNU/Linux	SH-5/SH64 support in sh*-*-linux*
>>  SH-5/SH64 running OpenBSD 	SH-5/SH64 support in sh*-*-openbsd*
>>  
>> +* Aarch64/Linux hardware watchpoints improvements
>> +
>> +  Hardware watchpoints on unaligned addresses are now properly
>> +  supported when running Linux kernel 4.10 or higher: read and access
>> +  watchpoints are no longer spuriously missed, and all watchpoints
>> +  lengths between 1 and 8 bytes are supported.  On older kernels,
>> +  watchpoints set on unaligned addresses are no longer missed, with
>> +  the tradeoff that there is a possibility of false hits being
>> +  reported.
> 
> I wonder whether we need this NEWS entry.  We don't normally call out
> bugfixes there, do we?

Yao requested one in an earlier review.  I'm borderline about it
myself, with no strong opinion.
There's a tradeoff here, which may be worth advertising, and the
mention of kernel version might be useful too.

Thanks,
Pedro Alves


  reply	other threads:[~2018-04-20 15:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 21:08 Jan Kratochvil
2017-06-19 13:43 ` ping: " Jan Kratochvil
2017-06-19 13:44   ` Jan Kratochvil
2017-10-18 19:52 ` ping#2: " Jan Kratochvil
2017-10-30 11:27   ` Yao Qi
2017-11-03 22:04     ` Jan Kratochvil
2018-03-21 19:03       ` ping: " Jan Kratochvil
2018-04-20 14:49         ` Pedro Alves
2018-04-20 14:56           ` Pedro Alves
2018-04-20 15:54           ` Eli Zaretskii
2018-04-20 15:59             ` Pedro Alves [this message]
2018-04-26 20:12           ` Jan Kratochvil
2018-05-01 23:03             ` Jan Kratochvil
2018-05-01 23:06               ` Jan Kratochvil
2018-05-02 14:50                 ` Eli Zaretskii
2018-05-03  9:16                 ` Jan Kratochvil
2018-05-03  9:18                   ` Jan Kratochvil
2018-05-04 16:40                     ` Pedro Alves
2018-05-04 20:30                       ` [commit] " Jan Kratochvil
2018-05-04 20:47                         ` Pedro Alves
2018-05-07  8:03                           ` Omair Javaid
2018-05-07  8:36                             ` Jan Kratochvil
2018-05-08 12:08                 ` [patch] " Ulrich Weigand
2018-05-08 12:27                   ` [obv] watchpoint-unaligned.exp: Use skip_hw_watchpoint_tests [Re: [patch] aarch64: PR 19806: watchpoints: false negatives + PR 20207 contiguous ones] Jan Kratochvil
2018-05-08 12:45                     ` [obv] watchpoint-unaligned.exp: Use skip_hw_watchpoint_tests [Re: [patch] aarch64: PR 19806: watchpoints: false negatives + PR Ulrich Weigand
2017-10-30 11:31   ` ping#2: [patch] aarch64: PR 19806: watchpoints: false negatives + PR 20207 contiguous ones Yao Qi

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=8d4d9262-305c-eb71-8752-80d729e0cc6a@redhat.com \
    --to=palves@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=qiyaoltc@gmail.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