public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Schimpe, Christina" <christina.schimpe@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/1] gdb: Deprecate MPX commands.
Date: Thu, 07 Mar 2024 14:34:35 +0200	[thread overview]
Message-ID: <86zfva1aqs.fsf@gnu.org> (raw)
In-Reply-To: <20240307121111.2010241-1-christina.schimpe@intel.com>

> From: "Schimpe, Christina" <christina.schimpe@intel.com>
> Date: Thu,  7 Mar 2024 12:11:11 +0000
> 
> This patch deprecates the MPX commands "show/set mpx bound".
> Intel listed Intel(R) Memory Protection Extensions (MPX) as removed
> in 2019.  Following gcc v9.1, the linux kernel v5.6 and glibc v2.35,
> deprecate MPX in GDB.
> ---
>  gdb/NEWS            | 3 +++
>  gdb/doc/gdb.texinfo | 3 +++
>  gdb/i386-tdep.c     | 6 ++++--
>  3 files changed, 10 insertions(+), 2 deletions(-)

Thanks.

> diff --git a/gdb/NEWS b/gdb/NEWS
> index 2638b3e0d9c..d8ac0bb06a7 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -3,6 +3,9 @@
>  
>  *** Changes since GDB 14
>  
> +* The MPX commands "show/set mpx bound" have been deprecated, as Intel
> +  listed MPX as removed in 2019.

This part is okay.

> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -26652,6 +26652,9 @@ whose bounds are to be changed, @var{lbound} and @var{ubound} are new values
>  for lower and upper bounds respectively.
>  @end table
>  
> +Both commands are deprecated and will be removed in future versions of
> +@value{GDBN}.  MPX itself was listed as removed by Intel in 2019.

"Will be removed" or "might be removed"?  IOW, are we certain we will
definitely remove this, or do we just want to warn users that we
might?

Reviewed-By: Eli Zaretskii <eliz@gnu.org>

  reply	other threads:[~2024-03-07 12:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 12:11 Schimpe, Christina
2024-03-07 12:34 ` Eli Zaretskii [this message]
2024-03-07 12:40   ` Schimpe, Christina
2024-03-07 13:10     ` Eli Zaretskii
2024-03-07 13:30     ` Joel Brobecker
2024-03-08 16:20 ` Tom Tromey
2024-03-12 14:35   ` Schimpe, Christina

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=86zfva1aqs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=christina.schimpe@intel.com \
    --cc=gdb-patches@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).