public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] valgrind: update to 3.11.0
Date: Tue, 15 Dec 2015 12:43:46 -0800	[thread overview]
Message-ID: <775EDF49-40CC-432D-861A-0A67CA0630CD@gmail.com> (raw)
In-Reply-To: <4098937.xBsQpXnxS0@peggleto-mobl.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]


> On Dec 15, 2015, at 12:16 PM, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
> 
> On Tue, 15 Dec 2015 12:07:48 Andre McCurdy wrote:
>> On Tue, Dec 15, 2015 at 9:26 AM, Paul Eggleton
>> 
>> <paul.eggleton@linux.intel.com> wrote:
>>> On Tue, 15 Dec 2015 17:28:59 Alexander Kanavin wrote:
>>>> On 12/15/2015 05:25 PM, Martin Jansa wrote:
>>>>>> +COMPATIBLE_HOST = '(i.86|x86_64|mips|powerpc|powerpc64).*-linux'
>>>>>> +COMPATIBLE_HOST_armv7a = 'arm.*-linux'
>>>>> 
>>>>> Can you add armv7ve as well?
>>>> 
>>>> Armv7ve support is not yet in master, so you'll have to add it later I'm
>>>> afraid.
>>> 
>>> I think by policy we don't have any restrictions on architecture-specific
>>> flags in OE-Core (at least, assuming they're reasonable).
>> 
>> If we're going to duplicate all _armv7a over-rides for _armv7ve then
>> I'd vote to do so in a single patch series which fixes up the whole of
>> oe-core rather than adding the over-rides one at a time amongst
>> version updates etc.
> 
> Makes sense, but before doing that would it make sense to have a grouping
> override for all of them that can be used instead (where appropriate)?
> 

stepping back a step. What so different about armv7ve that it needs to be a separate arch
its just virtual extensions on top of armv7a, so any override pertaining to armv7a should
be valid for it well. Can you work towards making it so ?

> Cheers,
> Paul
> 
> --
> 
> Paul Eggleton
> Intel Open Source Technology Centre
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

  reply	other threads:[~2015-12-15 20:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15 15:02 [PATCH] valgrind: update to 3.11.0 Alexander Kanavin
2015-12-15 15:25 ` Martin Jansa
2015-12-15 15:28   ` Alexander Kanavin
2015-12-15 17:26     ` Paul Eggleton
2015-12-15 20:07       ` Andre McCurdy
2015-12-15 20:16         ` Paul Eggleton
2015-12-15 20:43           ` Khem Raj [this message]
2015-12-15 22:27             ` Andre McCurdy
2015-12-16  1:50               ` Khem Raj
2015-12-16  3:11                 ` Andre McCurdy
2015-12-16  5:03                   ` Khem Raj
2016-01-05 17:50 ` Burton, Ross
2016-01-07 14:24   ` alexander.kanavin

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=775EDF49-40CC-432D-861A-0A67CA0630CD@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.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