Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>, "Burton, Ross" <ross.burton@intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc-runtime: Add libmpx supprt for x86
Date: Sat, 04 Mar 2017 10:54:29 +0000	[thread overview]
Message-ID: <1488624869.22968.8.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1sqB7A9m2osnv9bwywRF5hT4-oNgKU+rLNyA8SD70n8Mbg@mail.gmail.com>

On Fri, 2017-03-03 at 14:58 -0800, Khem Raj wrote:
> On Fri, Mar 3, 2017 at 2:54 PM, Burton, Ross <ross.burton@intel.com>
> wrote:
> > 
> > 
> > On 3 March 2017 at 21:39, Khem Raj <raj.khem@gmail.com> wrote:
> > > 
> > > 
> > > > 
> > > > Enabling building the Intel Memory Protection Extension library
> > > > for x86.
> > > > 
> > > hope this works on amd chips as well ?
> > 
> > https://en.wikipedia.org/wiki/Intel_MPX
> > 
> > It depends on new instructions, so you'll have to ask AMD. :)
> OK if its not so then perhaps a bbappend in meta-intel is more
> appropriate.

Well, its part of gcc, not something meta-intel is patching in and its
a standard which other arches can implement, maybe in their own library
so I believe the recipe is the better place for this to live. I just
copied the description from the code iirc.

Incidentally, this fails to build on musl so I've just disabled it on
musl for now.

Cheers,

Richard


  reply	other threads:[~2017-03-04 10:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 11:54 [PATCH] gcc-runtime: Add libmpx supprt for x86 Richard Purdie
2017-03-03 21:39 ` Khem Raj
2017-03-03 22:54   ` Burton, Ross
2017-03-03 22:58     ` Khem Raj
2017-03-04 10:54       ` Richard Purdie [this message]
2017-03-04 18:58         ` Khem Raj
2017-03-08  0:00           ` Martin Jansa
2017-03-08 11:34             ` Richard Purdie

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=1488624869.22968.8.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=ross.burton@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