public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Walfred Tedeschi <walfred.tedeschi@intel.com>
To: Pedro Alves <palves@redhat.com>, eliz@gnu.org, brobecker@adacore.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH V5 4/5] Adaptation of siginfo fixup for the new bnd fields
Date: Tue, 02 Feb 2016 13:58:00 -0000	[thread overview]
Message-ID: <56B0B618.2040400@intel.com> (raw)
In-Reply-To: <56B08588.3080307@redhat.com>

Am 2/2/2016 um 11:31 AM schrieb Pedro Alves:
> (Moving your reply to this here, so we can keep this topic's
> conversation properly threaded.)
>
> Walfred Tedeschi wrote:
>
> On 01/28/2016 12:37 PM, Pedro Alves wrote:
>> On 01/22/2016 02:54 PM, Walfred Tedeschi wrote:
>>
>>> Caveat: No support for MPX on x32.
>>
>> What would it take to support that?
>
>> About your question on x32 and MPX.
>> MPX does not support 32bit pointers in 64bit mode.
>
> Ok, so IIUC, it's not a GDB limitation, or a limitation of this patch set.
> It's really that x32 can't support MPX at all.  Correct?
>
> Thanks,
> Pedro Alves
>

That is correct.

Thanks,
-Fred




Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

  reply	other threads:[~2016-02-02 13:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 15:36 [PATCH V5 0/5] Intel MPX bound violation support Walfred Tedeschi
2016-01-22 15:17 ` [PATCH V5 4/5] Adaptation of siginfo fixup for the new bnd fields Walfred Tedeschi
2016-01-28 12:37   ` Pedro Alves
2016-02-02 10:31     ` Pedro Alves
2016-02-02 13:58       ` Walfred Tedeschi [this message]
2016-01-22 15:17 ` [PATCH V5 1/5] Preparation for new siginfo on Linux Walfred Tedeschi
2016-01-28 12:20   ` Pedro Alves
2016-01-22 15:17 ` [PATCH V5 3/5] Add bound related fields to the siginfo structure Walfred Tedeschi
2016-01-28 12:23   ` Pedro Alves
2016-01-22 15:18 ` [PATCH V5 5/5] ntel MPX bound violation handling Walfred Tedeschi
2016-01-28 13:43   ` Pedro Alves
2016-01-28 13:49     ` Walfred Tedeschi
2016-01-28 14:18       ` Pedro Alves
2016-02-02 10:09     ` Walfred Tedeschi
2016-02-02 10:38       ` Pedro Alves
2016-02-02 10:41         ` Walfred Tedeschi
2016-01-22 15:18 ` [PATCH V5 2/5] Use linux_get_siginfo_type_with_fields for x86 Walfred Tedeschi
2016-01-28 12:19   ` Pedro Alves

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=56B0B618.2040400@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).