From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: armhf support in OpenEmbedded?
Date: Mon, 6 Feb 2012 15:22:57 -0600 [thread overview]
Message-ID: <4F3044B1.1000705@windriver.com> (raw)
In-Reply-To: <2025C8A2-8B17-4F99-B4B3-3A0C8EC2C322@dominion.thruhere.net>
On 2/6/12 3:17 PM, Koen Kooi wrote:
>
> Op 6 feb. 2012, om 22:01 heeft Leon Woestenberg het volgende geschreven:
>
>> Hello,
>>
>> do we already have support for the ARM "armhf" ABI in OpenEmbedded? (A quick search on the ML didn't get me hits).
>>
>> Basically,"armhf" is built with -mfloat-abi=hard, and tuned for armv7-a CPUs.
>
> Yes, we've had it for ages in OE-classic and Marks tune overhaul made it easy to use in OE-core as well. Also note that armhf has practically no adavantage over softfp in real world applications. The only things getting a decent speedup in proper benchmarks was povray.
I strongly discourage people from using it. If you don't care about ABI
compatibility it might be a few cycles faster.. but it does limit your ability
to draw from existing EABI software. (Be it commercial or open source.)
(And yes, I realize this is a minor concern for most embedded systems.. but it
is an issue.)
--Mark
> regards,
>
> Koen
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2012-02-06 21:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 21:01 armhf support in OpenEmbedded? Leon Woestenberg
2012-02-06 21:17 ` Mark Hatle
2012-02-06 21:17 ` Koen Kooi
2012-02-06 21:22 ` Mark Hatle [this message]
2012-02-06 21:40 ` Leon Woestenberg
2012-02-07 7:49 ` Koen Kooi
2012-02-06 22:44 ` Philip Balister
2012-02-06 21:21 ` Phil Blundell
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=4F3044B1.1000705@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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