[U-Boot] reasons for armv5 as default

[Alexander Holler <holler@ahsoftware.de>]

Am 19.02.2011 16:40, schrieb Alexander Holler:
> Hello,
>
> Am 19.02.2011 16:32, schrieb Albert ARIBAUD:
>
>> Granted :) -- the best option would be to have "-float-abi=none", but
>> that does not exist, and I prefer to be sure that if some poor soul puts
>> floating point code in U-Boot then at least it is going to work for all
>> platforms, so I'll keep -msoft-float in here.
>
> Hmm, but as we've seen, that doesn't work for all platforms because you
> can't mix softfloat and hardfloat. So using softfloat breaks building on
> (default-) hardfloat platforms if some poor soul puts floating point
> code in (which requires hardfloat-libraries too).
>
> So I still think going with the default option would be the right way to
> go. ;)


Btw, while we are there, is there any reason, besides being carefull, 
why u-boot for arm is compiled with -march=armv5(te) by default?

I'm just curious if there are some reasons for not using march=amrv7a 
for armv7 platforms and don't want to start a discussion about removing 
that default.

I've seen some comments about armv5, e.g. in 
arch/arm/cpu/armv7/omap3/cache.S, but I'm missing the knowledge to 
understand them.

Regards,

Alexander