From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mplayer: fix compilation of NEON assembly in libavcodec
Date: Mon, 15 Oct 2012 21:05:20 +0200 [thread overview]
Message-ID: <507C5E70.1050808@mind.be> (raw)
In-Reply-To: <87txtwxm2n.fsf@macbook.be.48ers.dk>
On 15/10/12 08:53, Peter Korsgaard wrote:
> Peter> It is? I've never done any real work on platforms with neon, so it's
> Peter> certainly a bit fussy to me, but I don't understand what the relation is
> Peter> with the calling convention.
>
> Peter> Aren't the new linaro toolchains hardfp and support neon?
>
> Peter> Googling a bit I see stuff like:
>
> Peter> http://wiki.meego.com/ARM/hardfp
> Peter> http://sources.redhat.com/ml/crossgcc/2012-07/msg00091.html
>
> Peter> http://wiki.debian.org/ArmHardFloatPort#GCC_floating-point_options
> Peter> mentions that neon + hardfp abi isn't supported by GCC 4.4, but
> Peter> otherwise doesn't mention that it cannot work.
>
> Any comments on this?
Sorry, I was going to test it with a Linaro toolchain but forgot about it.
Running it now.
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
next prev parent reply other threads:[~2012-10-15 19:05 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
2012-10-15 6:53 ` Peter Korsgaard
2012-10-15 19:05 ` Arnout Vandecappelle [this message]
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=507C5E70.1050808@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox