From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11996] opencv3 SIGILL on Cortex-A5 with VFPv4-D16
Date: Mon, 01 Jul 2019 21:47:09 +0000 [thread overview]
Message-ID: <bug-11996-163-b3eE6ncpmK@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11996-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11996
--- Comment #1 from Arnout Vandecappelle <arnout@mind.be> ---
> I think this code in opencv3.mk is wrong (or maybe the ARM fpu config options
> are wrong):
>
> 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
>
> Apparently I have BR2_ARM_CPU_HAS_VFPV3 set (even though I only have the
> -D16 version), but when you pass -DENABLE_VFPV3=ON to OpenCV, it passes
> -mfpu=vfpv3 to the compiler and this is what's causing the SIGILL.
If the only thing that ENABLE_VFPV3 does is to set the -mfpu=... option, then
we should just always set it to OFF, because we already pass that option.
Same for NEON, by the way.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-07-01 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 17:17 [Buildroot] [Bug 11996] New: opencv3 SIGILL on Cortex-A5 with VFPv4-D16 bugzilla at busybox.net
2019-07-01 21:47 ` bugzilla at busybox.net [this message]
2019-11-27 22:20 ` [Buildroot] [Bug 11996] " bugzilla at busybox.net
2020-02-05 16:49 ` bugzilla at busybox.net
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=bug-11996-163-b3eE6ncpmK@https.bugs.busybox.net/ \
--to=bugzilla@busybox.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