[yocto] GCC on ARM

[Gary Thomas]

On 2017-03-31 07:07, Khem Raj wrote:
>
>
> On 3/30/17 9:07 PM, Gary Thomas wrote:
>> [slightly off-topic]
>>
>> I work with a number of embedded ARM devices, all with different
>> processors, hence somewhat different tuning and build directories:
>>   Raspberry-Pi (1,2,3 - mostly 3):
>>     TUNE_FEATURES     = "arm armv7ve vfp thumb neon vfpv4
>> callconvention-hard cortexa7"
>>     build dirs:
>>       tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi
>>   BeagleBoneBlack:
>>     TUNE_FEATURES     = "arm armv7a vfp thumb neon callconvention-hard"
>>     build dirs:
>>       tmp/work/armv7ahf-neon-poky-linux-gnueabi
>>   i.MX6:
>>     TUNE_FEATURES     = "arm armv7a vfp thumb neon callconvention-hard
>> cortexa9"
>>     build dirs:
>>       tmp/work/cortexa9hf-neon-poky-linux-gnueabi
>>       tmp/work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi
>>       tmp/work/cortexa9t2hf-neon-mx6qdl-poky-linux-gnueabi
>>
>> What I'm wondering is, except for the obvious programs that use SoC
>> specific
>> functions like the IPU/GPU on the i.MX6, how different are these
>> really?  So
>> much so that they have to all have unique binaries?  Surely I could build
>> busybox or python and run the same binary on all three?
>>
>
> You can chose a least common denominator and use that as DEFAULTTUNE for
> all your machines. May be like armv7at2-neon

That's good to know, thanks.

What would I be giving up?  Anything of substance/importance?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------