Hello,<br><br><div class="gmail_quote">On Mon, Feb 6, 2012 at 10:22 PM, Mark Hatle <span dir="ltr"><<a href="mailto:mark.hatle@windriver.com">mark.hatle@windriver.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 2/6/12 3:17 PM, Koen Kooi wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Op 6 feb. 2012, om 22:01 heeft Leon Woestenberg het volgende geschreven:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
do we already have support for the ARM "armhf" ABI in OpenEmbedded? (A quick search on the ML didn't get me hits).<br>
Basically,"armhf" is built with -mfloat-abi=hard, and tuned for armv7-a CPUs.<br>
</blockquote>
<br>
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.<br>
</blockquote>
<br></div>
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.)<br>
</blockquote><div><br>Can someone please lift that large rock I have been under for ages?<br><br>Thanks!<br><br>Leon<br><br><br>/me climbing back into the OE trenches<br></div></div>