Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Schimpe, Christina" <christina.schimpe@intel.com>
Cc: gdb-patches@sourceware.org, felix.willgerodt@intel.com,
	luis.machado@arm.com
Subject: Re: [PATCH v4 2/2] LAM: Enable tagged pointer support for watchpoints.
Date: Thu, 04 Jul 2024 17:02:27 +0300	[thread overview]
Message-ID: <86r0c98dcc.fsf@gnu.org> (raw)
In-Reply-To: <SN7PR11MB763893D331E431FD5588B4F8F9DE2@SN7PR11MB7638.namprd11.prod.outlook.com> (christina.schimpe@intel.com)

> From: "Schimpe, Christina" <christina.schimpe@intel.com>
> CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>, "Willgerodt,
>  Felix" <felix.willgerodt@intel.com>, "luis.machado@arm.com"
> 	<luis.machado@arm.com>
> Date: Thu, 4 Jul 2024 13:05:35 +0000
> 
> > > diff --git a/gdb/NEWS b/gdb/NEWS
> > > index 47677cb773a..fcbb89e8bf8 100644
> > > --- a/gdb/NEWS
> > > +++ b/gdb/NEWS
> > > @@ -3,6 +3,8 @@
> > >
> > >  *** Changes since GDB 15
> > >
> > > +* GDB now supports watchpoints for tagged data pointers on amd64.
> > > +
> > >  * Debugger Adapter Protocol changes
> > 
> > Thanks.  The above NEWS text is okay, but I wonder whether we explain
> > anywhere what are "tagged data pointers".
> > 
> > Reviewed-By: Eli Zaretskii <eliz@gnu.org>
> 
> Thanks for the review. I understand this can be a bit confusing. 
> Is " GDB now supports watchpoints for tagged pointers used for data accesses on amd64." better?
> Or, we could also just write: " GDB now supports watchpoints for tagged pointers on amd64.", as watchpoints are usually just data breakpoints.
> 
> What do you think?

My bother is actually about what we say in the manual, not in NEWS.
If the manual explains this terminology, it is fine to leave it
unexplained in NEWS, as users are expected to turn to the manual for
the details of the NEWS entries they are interested in.  But if this
is not explained in the manual, then we should either explain it, or
do that in NEWS entry itself, and in the latter case I'm afraid your
suggestion above is not enough because "tagged pointers" are not
explained anywhere, either.

      parent reply	other threads:[~2024-07-04 14:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04 10:17 [PATCH v4 0/2] Add amd64 LAM watchpoint support Schimpe, Christina
2024-07-04 10:17 ` [PATCH v4 1/2] gdb: Make tagged pointer support configurable Schimpe, Christina
2024-07-04 10:17 ` [PATCH v4 2/2] LAM: Enable tagged pointer support for watchpoints Schimpe, Christina
2024-07-04 12:37   ` Willgerodt, Felix
2024-07-04 12:52   ` Eli Zaretskii
2024-07-04 13:05     ` Schimpe, Christina
2024-07-04 13:15       ` Schimpe, Christina
2024-07-04 14:06         ` Eli Zaretskii
2024-07-05  8:53           ` Schimpe, Christina
2024-07-05 10:47             ` Eli Zaretskii
2024-07-08  8:52               ` Schimpe, Christina
2024-07-08 11:42                 ` Eli Zaretskii
2024-07-08 14:25                   ` Schimpe, Christina
2024-07-08 14:53                     ` Eli Zaretskii
2024-07-08 14:57                       ` Schimpe, Christina
2024-07-04 14:02       ` Eli Zaretskii [this message]

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=86r0c98dcc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=christina.schimpe@intel.com \
    --cc=felix.willgerodt@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@arm.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