From: Walfred Tedeschi <walfred.tedeschi@intel.com>
To: palves@redhat.com, eliz@gnu.org, brobecker@adacore.com
Cc: gdb-patches@sourceware.org,
Walfred Tedeschi <walfred.tedeschi@intel.com>
Subject: [PATCH V4 0/2] BND register initialization
Date: Wed, 02 Mar 2016 16:21:00 -0000 [thread overview]
Message-ID: <1456935689-1820-1-git-send-email-walfred.tedeschi@intel.com> (raw)
Former patch series for Intel(R) MPX ABI was converted into
two patches.
1. Initialization of bnd registers previous of performing inferior calls.
2. Addition of mpx-bnd-init-on-return setting.
The initialization of bnd registers was added also for i386, instead of concentrating
all code for amd64.
On the other hand the patch introducing the POINTER class, submitted
in V3, was removed.
Thanks again for your review,
-Fred
Walfred Tedeschi (2):
Initialize bnd register before performing inferior calls.
Add mpx-bnd-init-on-return set/show command for inferior calls.
gdb/NEWS | 4 +
gdb/amd64-tdep.c | 60 +++++++++++++++
gdb/doc/gdb.texinfo | 20 +++++
gdb/i386-tdep.c | 72 +++++++++++++++++-
gdb/i387-tdep.h | 3 +
gdb/testsuite/gdb.arch/i386-mpx-call.c | 126 +++++++++++++++++++++++++++++++
gdb/testsuite/gdb.arch/i386-mpx-call.exp | 92 ++++++++++++++++++++++
7 files changed, 376 insertions(+), 1 deletion(-)
create mode 100644 gdb/testsuite/gdb.arch/i386-mpx-call.c
create mode 100644 gdb/testsuite/gdb.arch/i386-mpx-call.exp
--
2.1.4
next reply other threads:[~2016-03-02 16:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 16:21 Walfred Tedeschi [this message]
2016-03-02 16:21 ` [PATCH V4 1/2] Initialize bnd register before performing inferior calls Walfred Tedeschi
2016-03-16 14:57 ` Luis Machado
2016-03-02 16:21 ` [PATCH V4 2/2] Add mpx-bnd-init-on-return set/show command for " Walfred Tedeschi
2016-03-02 16:35 ` Eli Zaretskii
2016-03-03 11:04 ` Walfred Tedeschi
2016-03-03 20:34 ` Eli Zaretskii
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=1456935689-1820-1-git-send-email-walfred.tedeschi@intel.com \
--to=walfred.tedeschi@intel.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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).