From: "Schimpe, Christina" <christina.schimpe@intel.com>
To: Tom Tromey <tom@tromey.com>, Eli Zaretskii <eliz@gnu.org>,
Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 1/1] gdb: Deprecate MPX commands.
Date: Tue, 12 Mar 2024 14:35:43 +0000 [thread overview]
Message-ID: <SN7PR11MB7638FF4F8BBC5AFA99CE1B7EF92B2@SN7PR11MB7638.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87bk7osnj1.fsf@tromey.com>
Hi all,
Thank you for the review. I've pushed the patch now.
Christina
> -----Original Message-----
> From: Tom Tromey <tom@tromey.com>
> Sent: Friday, March 8, 2024 5:21 PM
> To: Schimpe, Christina <christina.schimpe@intel.com>
> Cc: gdb-patches@sourceware.org
> Subject: Re: [PATCH 1/1] gdb: Deprecate MPX commands.
>
> >>>>> Schimpe, Christina <christina.schimpe@intel.com> writes:
>
> > 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.
>
> Thank you. The code parts are ok.
> Approved-By: Tom Tromey <tom@tromey.com>
>
> Tom
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
prev parent reply other threads:[~2024-03-12 14:35 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
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 [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=SN7PR11MB7638FF4F8BBC5AFA99CE1B7EF92B2@SN7PR11MB7638.namprd11.prod.outlook.com \
--to=christina.schimpe@intel.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).