From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] mpg123 segfaults on A8 (imx53)
Date: Wed, 31 Oct 2012 00:04:37 +0100 [thread overview]
Message-ID: <50905D05.5010000@mind.be> (raw)
In-Reply-To: <1A05C4080C29496381D223141719DD30@JohanW7>
On 10/30/12 11:08, Sagaert Johan wrote:
> So i had a look at the configuration options and i think it might have something to do the the option --with-cpu not
> being correct..
arm_nofpu should work for any ARM processor...
> I tried :
> MPG123_CPU = neon
> But the build fails:
> ....
> dct64_neon_float.S:125: Error: selected processor does not support ARM mode `vmul.f32 q7,q11,q14'
> dct64_neon_float.S:127: Error: selected processor does not support ARM mode `vdup.32 q12,d31[0]'
> dct64_neon_float.S:128: Error: selected processor does not support ARM mode `vmov d31,d30'
> dct64_neon_float.S:130: Error: selected processor does not support ARM mode `vsw
> ....
Depending on how the toolchain is compiled, you may need to add
-mfloat-abi=softfp -mfpu=neon or -mfloat-abi=hard -mfpu=neon to the CFLAGS
to get neon support.
But I doubt that that's the issue - illegal instructions give SIGILL, not
SIGSEGV. So your only option is to debug mpg123 with gdbserver or valgrind.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2012-10-30 23:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 10:08 [Buildroot] mpg123 segfaults on A8 (imx53) Sagaert Johan
2012-10-30 23:04 ` Arnout Vandecappelle [this message]
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=50905D05.5010000@mind.be \
--to=arnout@mind.be \
--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.