From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/opencv3: disable NEON and VFPv3 options
Date: Wed, 5 Feb 2020 17:52:28 +0100 [thread overview]
Message-ID: <20200205175228.148236d5@windsurf> (raw)
In-Reply-To: <20190820184039.28611-1-fontaine.fabrice@gmail.com>
Hello,
On Tue, 20 Aug 2019 20:40:39 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> -# * PowerPC support is turned off since its only effect is altering CFLAGS,
> -# adding '-mcpu=G3 -mtune=G5' to them, which is already handled by Buildroot.
> +# * PowerPC, NEON and VFPv3 support are turned off since their only effects are
> +# altering CFLAGS, adding '-mcpu=G3 -mtune=G5', '-mfpu=neon' or '-mfpu=vfpv3'
> +# to them, which is already handled by Buildroot.
> OPENCV3_CONF_OPTS += \
> -DENABLE_POWERPC=OFF \
> - -DENABLE_NEON=$(if $(BR2_ARM_CPU_HAS_NEON),ON,OFF)
> -
> -ifeq ($(BR2_ARCH_IS_64):$(BR2_ARM_CPU_HAS_VFPV3),:y)
> -OPENCV3_CONF_OPTS += -DENABLE_VFPV3=ON
> -else
> -OPENCV3_CONF_OPTS += -DENABLE_VFPV3=OFF
> -endif
> + -DENABLE_NEON=OFF \
> + -DENABLE_VFPV3=OFF
>
> # Cuda stuff
> OPENCV3_CONF_OPTS += \
So, we looked into it some more with Arnout, and turns out that
ENABLE_NEON=ON does more than adding options to CFLAGS, it enables some
NEON specific code in the Carotene sublibrary at least.
However, for VFPv3 indeed it is true that it was only adding CFLAGS. So
we reduced the patch to just do -DENABLE_VFPV3=OFF, and applied.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-02-05 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 18:40 [Buildroot] [PATCH 1/1] package/opencv3: disable NEON and VFPv3 options Fabrice Fontaine
2020-02-05 16:52 ` Thomas Petazzoni [this message]
2020-03-10 21:33 ` Peter Korsgaard
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=20200205175228.148236d5@windsurf \
--to=thomas.petazzoni@bootlin.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