public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCHv2][RFC] arch-armv7ve.inc: respect armv7a override as well
Date: Fri, 8 Jan 2016 18:00:54 +0100	[thread overview]
Message-ID: <20160108170054.GB2573@jama> (raw)
In-Reply-To: <CAJ86T=WNGGp=L358DSu2+VXM4eEdOz9FRcDBkGueUap80RjGBw@mail.gmail.com>

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

On Fri, Jan 08, 2016 at 08:24:36AM -0800, Andre McCurdy wrote:
> On Fri, Jan 8, 2016 at 4:44 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > * in all cases we currently have we consider armv7ve to be compatible with armv7a
> 
> Is this a short term workaround or a long term solution?

It's just RFC for discussion.

> If it's a long term solution then how will armv7m and armv7r be
> handled? They are likely to need to duplicate a lot of the current
> armv7a over-rides too.

armv7a and armv7ve are much closer than armv7a and armv7m or armv7r as
Khem said in earlier discussion. And maybe it's because fewer people use
armv7[rm], but currently these 2 aren't used anywhere as overrides (in
layers I've in world builds).

> Maybe adding a generic "armv7" over-ride which can be enabled by all
> armv7 variants is a better option?

Maybe, but that will change how armv7r and armv7m are currently built, I
cannot say if for better or worse, I don't use either.

> Either way, I'd like to continue cleaning up of the existing armv7a
> over-rides (e.g. the libav armv7a specific optimisation is likely
> bogus and should be removed, etc).
> 
> 
> > Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> > ---
> >  meta/conf/machine/include/arm/arch-armv7ve.inc | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/meta/conf/machine/include/arm/arch-armv7ve.inc b/meta/conf/machine/include/arm/arch-armv7ve.inc
> > index 79e1ef6..d0fdff7 100644
> > --- a/meta/conf/machine/include/arm/arch-armv7ve.inc
> > +++ b/meta/conf/machine/include/arm/arch-armv7ve.inc
> > @@ -3,7 +3,8 @@ DEFAULTTUNE ?= "armv7ve"
> >  TUNEVALID[armv7ve] = "Enable instructions for ARMv7ve"
> >  TUNECONFLICTS[armv7ve] = "armv4 armv5 armv6 armv7 armv7a"
> >  TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'armv7ve', ' -march=armv7ve', '', d)}"
> > -MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'armv7ve', 'armv7ve:', '' ,d)}"
> > +# In all cases we currently have we consider armv7ve to be compatible with armv7a
> > +MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'armv7ve', 'armv7ve:armv7a:', '' ,d)}"
> >
> >  require conf/machine/include/arm/arch-armv6.inc
> >  require conf/machine/include/arm/feature-arm-neon.inc
> > --
> > 2.7.0
> >
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2016-01-08 17:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08 12:36 [PATCH][RFC] arch-armv7ve.inc: respcet armv7a override as well Martin Jansa
2016-01-08 12:44 ` [PATCHv2][RFC] arch-armv7ve.inc: respect " Martin Jansa
2016-01-08 16:24   ` Andre McCurdy
2016-01-08 17:00     ` Martin Jansa [this message]
2016-01-08 18:24       ` Andre McCurdy
2016-01-08 20:44         ` Phil Blundell
2016-01-11 19:10         ` Khem Raj
2016-01-11 19:52           ` Phil Blundell
2016-01-11 20:03             ` Khem Raj
2016-01-11 19:53           ` Andre McCurdy
2016-01-08 20:13     ` Phil Blundell

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=20160108170054.GB2573@jama \
    --to=martin.jansa@gmail.com \
    --cc=armccurdy@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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