From: Philip Balister <philip@balister.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Enabling NEON instructions for fftw
Date: Thu, 03 Jan 2013 13:42:09 -0500 [thread overview]
Message-ID: <50E5D101.9030701@balister.org> (raw)
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.
Philip
next reply other threads:[~2013-01-03 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 18:42 Philip Balister [this message]
2013-01-03 19:21 ` Enabling NEON instructions for fftw Mark Hatle
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=50E5D101.9030701@balister.org \
--to=philip@balister.org \
--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 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.