From: "David Nyström" <david.c.nystrom@gmail.com>
To: Phil Blundell <pb@pbcl.net>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] x264: SPE is not compatible with Altivec
Date: Fri, 21 Feb 2014 22:45:47 +0100 [thread overview]
Message-ID: <5307C90B.3080804@gmail.com> (raw)
In-Reply-To: <1393017641.2640.21.camel@e130.pbcl.net>
On 2014-02-21 22:20, Phil Blundell wrote:
> On Fri, 2014-02-21 at 20:40 +0100, David Nystrom wrote:
>> Perhaps you know this already, but e500v2 is a cpu arch, same as
>> armv5.
> Is that really true? I thought e500v2 was an actual core and the
> equivalent architecture was Power v2.03 or something.
Yes, good point.
I understand Sauls concern.
>
>> For future reference, should all ppc related CPU-arch specific stuff
>> be directed to the FSL bsp ?
> Since we do ship tune-ppce500.inc in oe-core, I think it makes sense to
> also include the overrides necessary to make compilation work with SPE
> enabled. It doesn't seem unreasonable that users would expect that the
> recipes in oe-core would work with a configuration that comes as
> standard.
>
> However, adding overrides for e500v2 specifically does seem like a bad
> plan since we will then end up having to duplicate the thing for every
> other non-altivec configuration. Can you come up with some override
> that will apply to all SPE configurations,
Yep, will return with V2.
> or failing that a patch for
> the configure script that will disable the altivec assembler if it
> notices that ${CC} is configured for SPE?
>
> p.
>
>
next prev parent reply other threads:[~2014-02-21 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 13:56 [PATCH] x264: SPE is not compatible with Altivec David Nyström
2014-02-21 18:28 ` Saul Wold
2014-02-21 19:40 ` David Nystrom
2014-02-21 21:20 ` Phil Blundell
2014-02-21 21:45 ` David Nyström [this message]
2014-02-21 21:59 ` [PATCHv2] x246: Disable Altivec asm when SPE is enabled David Nyström
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=5307C90B.3080804@gmail.com \
--to=david.c.nystrom@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.