Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter Kümmel" <syntheticpp@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] FFTW optimized for ARM and NEON FPU
Date: Tue, 24 Feb 2015 10:44:40 +0100	[thread overview]
Message-ID: <54EC4808.3040209@gmx.net> (raw)
In-Reply-To: <54EBF694.6090705@gmail.com>

+FFTW_CONF_OPTS+= ARM_FLOAT_ABI=softfp

Shouldn't it use hardfp?
https://wiki.debian.org/ArmHardFloatPort/VfpComparison

Am 24.02.2015 um 04:57 schrieb guillaume william brs:
> Hello,
>
> I am working on a cortex-a9 (zynq SoC, mainly zc706)
> I faced fairly slow computations of FFT using this library
> with the default configuration (20MFlops).
>
> I modified package/fftw.mk to optimize the library
> compilation as long as an FPU is available,
> NEON in this case: this increased the number of MFlops to
> 500-600.
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>

  reply	other threads:[~2015-02-24  9:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24  3:57 [Buildroot] FFTW optimized for ARM and NEON FPU guillaume william brs
2015-02-24  9:44 ` Peter Kümmel [this message]
2015-03-15 23:41 ` 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=54EC4808.3040209@gmx.net \
    --to=syntheticpp@gmx.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox