From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Enabling NEON instructions for fftw
Date: Thu, 3 Jan 2013 13:21:26 -0600 [thread overview]
Message-ID: <50E5DA36.5090702@windriver.com> (raw)
In-Reply-To: <50E5D101.9030701@balister.org>
On 1/3/13 12:42 PM, Philip Balister wrote:
> So, recent versions of fftw have NEON support for the single precision
> build. In the poast, I just passed --enable-neon to configure or the
> armv7a case. Now, this is not entirely correct, since some armv7a's lack
> a NEON coprocessor.
>
> Does anyone have a suggestion for how to handle this better? Personally,
> I think if you want to run fftwf without NEON, you should have your head
> examined, but I would like to avoid generating packages that SIGILL on
> people.
This says to me that either you need a machine specific package, or use an
alternative architecture for that package.. (that is compatible).. then the
package can switch neon on/off depending on arch of tuning flags.
There is an armv7a-neon tuning defined. This enabled the TUNE_FEATURES of
'neon'. So you should be able to check for that in the fftw recipe, and enable
the --enable-neon when it's set. (Using PACKAGECONFIG is likely best...)
Then you can change the DEFAULTTUNE_<recipe> = "armv7-neon" in your local.conf.
--Mark
> Philip
>
> _______________________________________________
> 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:[~2013-01-03 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 18:42 Enabling NEON instructions for fftw Philip Balister
2013-01-03 19:21 ` Mark Hatle [this message]
2013-01-04 15:36 ` Philip Balister
2013-01-04 15:46 ` Mark Hatle
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=50E5DA36.5090702@windriver.com \
--to=mark.hatle@windriver.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