From: "H.J. Lu" <hjl.tools@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Walfred Tedeschi <walfred.tedeschi@intel.com>,
GDB <gdb-patches@sourceware.org>
Subject: Re: [PATCH v1] Intel(R) MPX registers to the DWARF enumeration.
Date: Sun, 06 Dec 2015 17:42:00 -0000 [thread overview]
Message-ID: <CAMe9rOqaj154UnzTX1GHPMtKpFdWRmk2BwwTMJi1esyXQXpPAw@mail.gmail.com> (raw)
In-Reply-To: <20151206163527.GA4819@adacore.com>
On Sun, Dec 6, 2015 at 8:35 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>> Add registers as defined in the ABI adapted for MPX.
>> As presented at:
>> https://github.com/hjl-tools/x86-psABI/wiki/X86-psABI
>>
>> 2013-05-06 Walfred Tedeschi <walfred.tedeschi@intel.com>
>>
>> * amd64-tdep.c (amd64_dwarf_regmap): Add mpx registers.
>> * amd64-tdep.h (amd64_regnum): Add mpx registers.
>
> Small nit: should we spell "MPX"?
>
> BTW - the ABI document reference above seem to only indicate
> registers 126-129 as "reserved" rather than bound registers 0-4.
> Is that normal?
>
We used to have DWARF register map for bound registers. But
it was determined that it isn't needed. If it isn't true, we need to
revisit it.
--
H.J.
next prev parent reply other threads:[~2015-12-06 17:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 15:09 [PATCH obv] Changing compiler flags for MPX tests Walfred Tedeschi
2015-10-26 16:10 ` [PATCH v1] Intel(R) MPX registers to the DWARF enumeration Walfred Tedeschi
2015-12-06 16:35 ` Joel Brobecker
2015-12-06 17:42 ` H.J. Lu [this message]
2015-12-07 8:29 ` Tedeschi, Walfred
2015-10-26 16:11 ` [PATCH v1] Synchronize siginfo type described in GDB with the kernel and glibc ones Walfred Tedeschi
2015-11-18 23:01 ` Joel Brobecker
2015-11-19 9:52 ` Tedeschi, Walfred
2015-11-19 13:27 ` Pedro Alves
2015-11-19 16:41 ` Tedeschi, Walfred
2015-11-19 17:07 ` Pedro Alves
2015-12-01 10:08 ` Tedeschi, Walfred
2015-12-01 12:08 ` Pedro Alves
2015-10-26 16:22 ` [PATCH v1] ABI changes for Intel(R) MPX Walfred Tedeschi
2015-10-26 19:07 ` Eli Zaretskii
2015-10-27 17:21 ` Tedeschi, Walfred
2015-12-06 16:16 ` Joel Brobecker
2015-10-26 16:25 ` [PATCH obv] Fix non stopping breakpoint on newer compilers Walfred Tedeschi
2015-11-04 14:42 ` Joel Brobecker
2015-10-26 16:26 ` [PATCH v1] Intel(R) MPX - Bound violation handling Walfred Tedeschi
2015-11-04 14:55 ` Joel Brobecker
2015-11-05 10:04 ` Tedeschi, Walfred
2015-11-19 0:01 ` Joel Brobecker
2015-12-14 17:43 ` Tedeschi, Walfred
2015-12-14 18:45 ` Pedro Alves
2015-12-15 11:01 ` Tedeschi, Walfred
2015-12-16 15:21 ` Tedeschi, Walfred
2015-12-16 16:52 ` Pedro Alves
2015-12-17 17:31 ` Tedeschi, Walfred
2015-12-21 17:23 ` Pedro Alves
2015-11-04 14:42 ` [PATCH obv] Changing compiler flags for MPX tests Joel Brobecker
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=CAMe9rOqaj154UnzTX1GHPMtKpFdWRmk2BwwTMJi1esyXQXpPAw@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=walfred.tedeschi@intel.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