From: "Tedeschi, Walfred" <walfred.tedeschi@intel.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: "tromey@redhat.com" <tromey@redhat.com>,
"jan.kratochvil@redhat.com" <jan.kratochvil@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 0/7] Intel(R) MPX registers support.
Date: Fri, 23 Aug 2013 13:40:00 -0000 [thread overview]
Message-ID: <AC542571535E904D8E8ADAE745D60B191B1463EA@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <201308231329.r7NDTtsJ018351@glazunov.sibelius.xs4all.nl>
Hello Mark,
Thanks a lot for your feedback!
I will work on it.
Thanks again and regards,
-Fred
-----Original Message-----
From: Mark Kettenis [mailto:mark.kettenis@xs4all.nl]
Sent: Friday, August 23, 2013 3:30 PM
To: Tedeschi, Walfred
Cc: Tedeschi, Walfred; tromey@redhat.com; jan.kratochvil@redhat.com; gdb-patches@sourceware.org
Subject: Re: [PATCH 0/7] Intel(R) MPX registers support.
> From: "Tedeschi, Walfred" <walfred.tedeschi@intel.com>
> Date: Thu, 22 Aug 2013 09:42:16 +0000
>
> Hello Mark,
>
> First of all thanks for your quick response!
>
> I am not sure if I understood your question right. I understood that
> you would like to have it at the bottom of the list always since it is
> a fake register. Is this right?
Right. Otherwise the generic (non-Linux) mappings end up with funny holes.
> In the current implementation, all numbers taken cannot be renumbered
> in upcoming new features or extensions. Only taking new slots is
> possible. In the case of the mentioned register it was already taken for amd64-linux.
> Please correct me if I am wrong here. ;)
The GDB internal registers can be renumbered. In fact we did this when the AVX support was added. What you cannot change is the layout of the registers in the various target descriptions, because those define the on-the-wire format used in the remote protocol. For the remote protocol, GDB automatically does the remapping. For the native debugger you'll have to make sure the relevant mappings in the *-linux-nat.c files are updated.
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
prev parent reply other threads:[~2013-08-23 13:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 12:46 Walfred Tedeschi
2013-08-21 12:46 ` [PATCH 1/7] Fix conditions in creating a bitfield Walfred Tedeschi
2013-08-21 12:46 ` [PATCH 7/7] Add MPX registers tests Walfred Tedeschi
2013-08-21 12:46 ` [PATCH 5/7] Add MPX support to gdbserver Walfred Tedeschi
2013-08-21 12:46 ` [PATCH 3/7] Add MPX support for i386 Walfred Tedeschi
2013-08-21 12:46 ` [PATCH 4/7] MPX for amd64 Walfred Tedeschi
2013-08-21 12:46 ` [PATCH 2/7] Add MPX registers XML files Walfred Tedeschi
2013-08-21 12:46 ` [PATCH 6/7] Add pretty-printer for MPX bnd registers Walfred Tedeschi
2013-08-21 14:33 ` [PATCH 0/7] Intel(R) MPX registers support Mark Kettenis
2013-08-21 16:25 ` Tedeschi, Walfred
2013-08-22 9:42 ` Tedeschi, Walfred
2013-08-23 13:30 ` Mark Kettenis
2013-08-23 13:40 ` Tedeschi, Walfred [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=AC542571535E904D8E8ADAE745D60B191B1463EA@IRSMSX104.ger.corp.intel.com \
--to=walfred.tedeschi@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
--cc=tromey@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