From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Adding TARGET_VECTOR
Date: Fri, 30 Sep 2011 10:31:35 -0700 [thread overview]
Message-ID: <4E85FCF7.6030208@gmail.com> (raw)
In-Reply-To: <5755C992-C736-4714-9DE3-761E3E74C6F8@kernel.crashing.org>
On 8/25/2011 7:35 AM, Kumar Gala wrote:
> We have some packages like flac that are aware of vectorization that may or may not exist on a given processor. I was wondering if adding something like TARGET_VECTOR similar to TARGET_FPU made sense as a way for recipes to decide on how to set various vectorization flags if needed.
>
> I was looking at this mostly from the PPC side in which we have:
>
> TARGET_VECTOR = "" /* processor has no vector hw */
> TARGET_VECTOR = "altivec" /* processor has AltiVec support */
> TARGET_VECTOR = "spe" /* processor has signal processing engine support */
> TARGET_VECTOR = "vsx" /* processor has Vector-Scalar Extension */
>
is target vector a property of FPU itself or is it a separate processing
unit in hardware.?
> Not sure what makes sense for x86, ARM, or MIPS.
>
> - k
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-09-30 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 14:35 Adding TARGET_VECTOR Kumar Gala
2011-09-02 14:32 ` Kumar Gala
2011-09-30 17:31 ` Khem Raj [this message]
2011-09-30 17:49 ` McClintock Matthew-B29882
2011-09-30 20:05 ` Khem Raj
2011-09-30 20:08 ` McClintock Matthew-B29882
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=4E85FCF7.6030208@gmail.com \
--to=raj.khem@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