From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-09-04
Date: Mon, 5 Sep 2016 16:15:47 -0300 [thread overview]
Message-ID: <CAAEAJfCmiL6T=P=s_2UwVAk4BxxjJCaxqqdDsjnN3UD_809MGQ@mail.gmail.com> (raw)
In-Reply-To: <20160905063032.D7B78102B17@stock.ovh.net>
Thomas,
On 5 September 2016 at 03:30, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
[..]
> arm | fio-fio-2.13 | NOK | http://autobuild.buildroot.net/results/6b318983a1a318d30acb9c25f17065fbc4a0302a
Tried to tackle this one, but it seems the problem is with the
external toolchain. Let me post the error here to make the
discussion easier:
In file included from
/home/test/autobuild/run/instance-0/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/include/endian.h:60:0,
from
/home/test/autobuild/run/instance-0/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/include/bits/waitstatus.h:64,
from
/home/test/autobuild/run/instance-0/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/include/stdlib.h:42,
from t/../flist.h:4,
from t/btrace2fio.c:9:
/home/test/autobuild/run/instance-0/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/include/bits/byteswap.h:
In function 'main':
/home/test/autobuild/run/instance-0/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/include/bits/byteswap.h:46:10:
fatal error: You must enable NEON instructions (e.g.
-mfloat-abi=softfp -mfpu=neon) to use these intrinsics.
return __builtin_bswap32 (__bsx);
^~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [t/btrace2fio.o] Error 1
AFAICS, the code doesn't directly use NEON intrinsics,
so it's not fio's fault. After some digging, I found
a gcc upstream report [1]. Quoting:
""
Note that `NEON` isn't enabled and there's no direct use
of NEON instructions/intrinsics in the code so the NEON
instructions must have been added by the optimizer.
Seemingly subtle change can make the error disappear.
""
Which is exaclty what I'm seeing here. The issue is fixed in gcc v6.2.
[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71056
--
Ezequiel Garc?a, VanguardiaSur
www.vanguardiasur.com.ar
next prev parent reply other threads:[~2016-09-05 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-09-04 Thomas Petazzoni
2016-09-05 19:15 ` Ezequiel Garcia [this message]
2016-09-13 15:42 ` Thomas Petazzoni
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='CAAEAJfCmiL6T=P=s_2UwVAk4BxxjJCaxqqdDsjnN3UD_809MGQ@mail.gmail.com' \
--to=ezequiel@vanguardiasur.com.ar \
--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.