This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH 2/N, MPX, x86_64] Intel MPX support in glibc for x86_64
- From: Richard Henderson <rth at twiddle dot net>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: "Zamyatin, Igor" <igor dot zamyatin at intel dot com>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
- Date: Wed, 09 Apr 2014 18:38:23 -0700
- Subject: Re: [PATCH 2/N, MPX, x86_64] Intel MPX support in glibc for x86_64
- Authentication-results: sourceware.org; auth=none
- References: <0EFAB2BDD0F67E4FB6CCC8B9F87D756942973E8E at IRSMSX101 dot ger dot corp dot intel dot com> <CAMe9rOpOjjj7-Dzq9=bL2POFO46K=sz2hmSshqNzHRV5chzXZg at mail dot gmail dot com> <5345D627 dot 50302 at twiddle dot net> <CAMe9rOqEvsq0Rt4Erk6m_HV9tYEp2kh9dQNYAi7D9ZwDA96tZQ at mail dot gmail dot com>
On 04/09/2014 05:12 PM, H.J. Lu wrote:
>> Wouldn't it be just as easy to do
>> .byte 0x66,0x0f,0x1b,0x84,0x24; .long LR_BND_OFFSET
>> after all, you know how and where that offset is going to be encoded.
> Sure. We can do that after verifying LR_BND_OFFSET >= 0x80.
No need for that, since the previous bytes have encoded the form that expects a
4-byte offset. The offset can be anything at all within those bytes.