From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mplayer: fix compilation of NEON assembly in libavcodec
Date: Wed, 10 Oct 2012 11:13:15 +0200 [thread overview]
Message-ID: <87d30qadw4.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <50749743.5010700@mind.be> (Arnout Vandecappelle's message of "Tue, 09 Oct 2012 23:29:39 +0200")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> Please document why this is needed (if it is) in the commit message and
>> resubmit, thanks.
Arnout> neon fpu (like vfp* fpu) can only be used with the softfp abi,
Arnout> so both are needed. This is kind of standard ARM knowledge :-)
It is? I've never done any real work on platforms with neon, so it's
certainly a bit fussy to me, but I don't understand what the relation is
with the calling convention.
Aren't the new linaro toolchains hardfp and support neon?
Googling a bit I see stuff like:
http://wiki.meego.com/ARM/hardfp
http://sources.redhat.com/ml/crossgcc/2012-07/msg00091.html
http://wiki.debian.org/ArmHardFloatPort#GCC_floating-point_options
mentions that neon + hardfp abi isn't supported by GCC 4.4, but
otherwise doesn't mention that it cannot work.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-10-10 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 23:03 [Buildroot] [PATCH] mplayer: fix compilation of NEON assembly in libavcodec Arnout Vandecappelle
2012-10-05 23:45 ` Sagaert Johan
2012-10-08 20:27 ` Peter Korsgaard
2012-10-09 21:29 ` Arnout Vandecappelle
2012-10-10 9:13 ` Peter Korsgaard [this message]
2012-10-15 6:53 ` Peter Korsgaard
2012-10-15 19:05 ` Arnout Vandecappelle
2012-10-15 20:49 ` Arnout Vandecappelle
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=87d30qadw4.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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.