This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 0/7] Intel(R) MPX registers support.
- From: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- To: walfred dot tedeschi at intel dot com
- Cc: walfred dot tedeschi at intel dot com, tromey at redhat dot com, jan dot kratochvil at redhat dot com, gdb-patches at sourceware dot org
- Date: Fri, 23 Aug 2013 15:29:55 +0200 (CEST)
- Subject: Re: [PATCH 0/7] Intel(R) MPX registers support.
- References: <1377089148-11844-1-git-send-email-walfred dot tedeschi at intel dot com> <201308211433 dot r7LEXaQ9000855 at glazunov dot sibelius dot xs4all dot nl> <AC542571535E904D8E8ADAE745D60B191B145728 at IRSMSX104 dot ger dot corp dot intel dot com> <AC542571535E904D8E8ADAE745D60B191B145B6E at IRSMSX104 dot ger dot corp dot intel dot com>
> 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.