All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter A. Bigot" <pab@pabigot.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: poor performance of OpenEmbedded on BeagleBoneBlack compared to Debian
Date: Thu, 04 Sep 2014 05:55:53 -0500	[thread overview]
Message-ID: <54084539.9040103@pabigot.com> (raw)
In-Reply-To: <CAMKF1srA8gnfNF+myYTSm+VHjBeGCWwAC22y2OmrKYnkJffuQg@mail.gmail.com>

On 09/04/2014 12:39 AM, Khem Raj wrote:
> On Wed, Sep 3, 2014 at 6:59 PM, Peter A. Bigot <pab@pabigot.com> wrote:
>> debian@beaglebone:~$ g++ -Ofast -mfloat-abi=hard -o card card.cpp
>>    debian@beaglebone:~$ time ./card > /dev/null
>>    real    4m54.846s
>>    user    4m54.627s
>>    sys     0m0.057s
>>
>> With poky master + meta-ti it runs this fast:
>>
>>    root@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


  reply	other threads:[~2014-09-04 10:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04  1:59 poor performance of OpenEmbedded on BeagleBoneBlack compared to Debian Peter A. Bigot
2014-09-04  2:46 ` Robert Nelson
2014-09-04 10:46   ` Peter A. Bigot
2014-09-04  5:39 ` Khem Raj
2014-09-04 10:55   ` Peter A. Bigot [this message]
2014-09-04 12:33     ` Dmytriyenko, Denys
  -- strict thread matches above, loose matches on Subject: below --
2014-09-04 14:50 poor performance of OpenEmbedded on, " Mikhail Zakharov
2014-09-04 15:00 ` Denys Dmytriyenko
2014-09-04 15:37   ` Peter A. Bigot
2014-09-04 15:41     ` Peter A. Bigot
2014-09-04 17:50       ` Peter A. Bigot
2014-09-04 15:48     ` Denys Dmytriyenko
2014-09-04 15:55       ` Robert Nelson
2014-09-04 18:10         ` Denys Dmytriyenko
2014-09-04 19:03           ` Robert Nelson
2014-09-04 19:09             ` Denys Dmytriyenko
2014-09-04 19:04           ` Peter A. Bigot
2014-09-04 19:07             ` Robert Nelson
2014-09-04 19:09               ` Robert Nelson
2014-09-04 19:41                 ` Denys Dmytriyenko
2014-09-04 15:55       ` Peter A. Bigot
2014-09-04 19:48         ` Khem Raj

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=54084539.9040103@pabigot.com \
    --to=pab@pabigot.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=raj.khem@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.