From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/7 v6] package/fftw: add ARM optimisations
Date: Mon, 16 Mar 2015 15:32:04 +0100 [thread overview]
Message-ID: <20150316143204.GC4271@free.fr> (raw)
In-Reply-To: <20150316153050.68ab2d76@x230.trabucayre.com>
Gwenhael, All,
On 2015-03-16 15:30 +0100, gwenhael.goavec spake thusly:
> Dear Yann E. MORIN
> On Mon, 16 Mar 2015 14:54:01 +0100
> "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> [SNIP]
> > choice
> > prompt "fftw precision"
> > default BR2_PACKAGE_FFTW_PRECISION_NONE
> > @@ -33,6 +36,7 @@ config BR2_PACKAGE_FFTW_PRECISION_SINGLE
> > bool "single precision"
> > select BR2_PACKAGE_FFTW_USE_SSE if BR2_X86_CPU_HAS_SSE
> > select BR2_PACKAGE_FFTW_USE_SSE2 if BR2_X86_CPU_HAS_SSE2
> > + select BR2_PACKAGE_FFTW_USE_NEON if BR2_ARM_FPU_NEON
> > help
> [SNIP]
> s/BR2_ARM_FPU_NEON/BR2_ARM_CPU_HAS_NEON/
No, because even if the CPU has NEON, it is not enough for NEOn to be
enabled.
That's what I initially tried, but it did not work, as fftw compiles
parts of its code without specifying -mfpu=neon, and thus it falls to
the value specified by Buildroot, and the compilation breaks.
I should probably have said so in the commit log, indeed...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-03-16 14:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 13:54 [Buildroot] [PATCH 0/7 v6] package/fftw: add a bunch of optimisations (branch yem/fftw) Yann E. MORIN
2015-03-16 13:53 ` [Buildroot] [PATCH 1/7 v6] fftw: add compile precision option Yann E. MORIN
2015-03-16 13:54 ` [Buildroot] [PATCH 2/7 v6] package/fftw: add x86 optimisations Yann E. MORIN
2015-03-16 13:54 ` [Buildroot] [PATCH 3/7 v6] package/fftw: add ARM optimisations Yann E. MORIN
2015-03-16 14:30 ` gwenhael.goavec
2015-03-16 14:32 ` Yann E. MORIN [this message]
2015-03-16 14:51 ` Thomas Petazzoni
2015-03-16 13:54 ` [Buildroot] [PATCH 4/7 v6] package/fftw: disable fortran Yann E. MORIN
2015-03-16 15:46 ` gwenhael.goavec
2015-03-16 13:54 ` [Buildroot] [PATCH 5/7 v6] package/fftw: enable threads when the tooclhain has them Yann E. MORIN
2015-03-16 15:48 ` gwenhael.goavec
2015-03-16 13:54 ` [Buildroot] [PATCH 6/7 v6] package/fftw: enable OpenMP if the compiler has that Yann E. MORIN
2015-03-16 16:16 ` gwenhael.goavec
2015-03-16 13:54 ` [Buildroot] [PATCH 7/7 v6] package/fftw: add option for fast maths Yann E. MORIN
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=20150316143204.GC4271@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.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.