<div dir="ltr">Hello,<br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 16, 2015 at 3:05 AM, J. Tang <span dir="ltr"><<a href="mailto:tang@jtang.org" target="_blank">tang@jtang.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
On 2015-01-15, at 04:06, Mike Looijmans <<a href="mailto:mike.looijmans@topic.nl">mike.looijmans@topic.nl</a>> wrote:<br>
<br>
> -2- The CPU doesn't actually have floating point support and the kernel is emulating it for you. This allows the platform to run "hf" binaries, at a minor performance cost compared to completely doing the emulation in user space (libc).<br>
<br>
</span>From my understanding, the Raspberry Pi (at least the model B, which is what I have) has an FPU.<br>
<br>
Would it hurt to at least mention in the top-level README of the meta-raspberrypi layer that a user could enable hard FP by setting the DEFAULTTUNE?<br>
<span class="im HOEnZb"><br></span></blockquote><div><br></div><div>Definitely it wouldn't. But right now we have two options:</div><div>We can just throw a README line and that's it.</div><div>Or we can  investigate a little to see if in our current setup we actually use FPU instructions or not. Following Mike's answer I would definitely think that we are in case 1 where the compile based on the CPU configuration figures out that we can use FPU instruction on this CPU architecture. Right now, as being on vacation, I can really test on binaries by dissembling code and check it by hand. Anybody who can do it and provide some feedback? As well, some bench-marking would really make sense here.<br></div></div><div class="gmail_extra"><br></div>Thanks guys.<br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div style="text-align:center"></div><div style="text-align:center"><div align="left"><b style="font-family:Arial;font-size:small;color:rgb(51,51,51);text-align:center">Andrei Gherzan</b><br></div></div></div></div>
</div></div>