[meta-ti] poor performance of OpenEmbedded on BeagleBoneBlack compared to Debian

[Dmytriyenko, Denys]

You should be fine, as meta-ti machines now force hardfp...


Sent from my Android phone using TouchDown (www.nitrodesk.com)

-----Original Message-----
From: Peter A. Bigot [pab at pabigot.com]
Received: Thursday, 04 Sep 2014, 6:56
To: Khem Raj [raj.khem at gmail.com]
CC: meta-ti at yoctoproject.org [meta-ti at yoctoproject.org]
Subject: Re: [meta-ti] poor performance of OpenEmbedded on BeagleBoneBlack compared to Debian

On 09/04/2014 12:39 AM, Khem Raj wrote:
> On Wed, Sep 3, 2014 at 6:59 PM, Peter A. Bigot <pab at pabigot.com> wrote:
>> debian at beaglebone:~$ g++ -Ofast -mfloat-abi=hard -o card card.cpp
>>    debian at beaglebone:~$ time ./card > /dev/null
>>    real    4m54.846s
>>    user    4m54.627s
>>    sys     0m0.057s
>>
>> With poky master + meta-ti it runs this fast:
>>
>>    root at beaglebone:~# time ./card > /dev/null
>>    real    9m37.901s
>>    user    9m37.200s
>>    sys     0m0.150s
>
> you should enable hardfloat ABI for poky as well for this kind of load.

Yeah, I remember that from the big argument back in oe-core, but what's
lacking in all that is any revelation of exactly how to do that.

The poky build using meta-ti's BSP for beaglebone puts gcc and
gcc-runtime into cortexa8t2hf-vfp-neon-poky-linux-gnueabi which AFAICT
is supposed to be hard-float.

-mfloat-abi=hard is being passed when gcc-runtime is built, and when the
application is built.

What toolchain-build or runtime-build enables hardfloat if that isn't
already being done?

Peter
--
_______________________________________________
meta-ti mailing list
meta-ti at yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-ti/attachments/20140904/1376effb/attachment.html>