Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs: nitrogen*: enable NEON support
Date: Fri, 16 Sep 2016 18:26:50 +0200	[thread overview]
Message-ID: <20160916182650.055f49d3@free-electrons.com> (raw)
In-Reply-To: <CAAMH-ysSivk0Q+-L0P9NTTbxwc53wAbfj4mTXZJ=auAKZTVVzQ@mail.gmail.com>

Hello,

On Fri, 16 Sep 2016 16:20:42 +0200, Gary Bisson wrote:

> Because the first two configurations are for i.MX6 (ARM Cortex-A9)
> whereas the last one is i.MX7 (ARM Cortex-A7).
> 
> So relying on Config.in.arm, the Cortex-A9 doesn't have VFPv4:
> https://git.buildroot.net/buildroot/tree/arch/Config.in.arm#n125
> https://git.buildroot.net/buildroot/tree/arch/Config.in.arm#n141

OK, then you should be using the VFPv3 instead of the NEON for FPU.
Indeed:

"""
     If the selected floating-point hardware includes the NEON extension
     (e.g.  '-mfpu'='neon'), note that floating-point operations are not
     generated by GCC's auto-vectorization pass unless
     '-funsafe-math-optimizations' is also specified.  This is because
     NEON hardware does not fully implement the IEEE 754 standard for
     floating-point arithmetic (in particular denormal values are
     treated as zero), so the use of NEON instructions may lead to a
     loss of precision.
"""

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-09-16 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-16 13:09 [Buildroot] [PATCH] configs: nitrogen*: enable NEON support Gary Bisson
2016-09-16 14:13 ` Thomas Petazzoni
2016-09-16 14:20   ` Gary Bisson
2016-09-16 16:26     ` Thomas Petazzoni [this message]
2016-09-16 16:44       ` Gary Bisson

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=20160916182650.055f49d3@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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