On 05/01/15 13:37, Tom Rini wrote:
On Mon, Jan 05, 2015 at 12:24:13PM +0000, B.R. Oake wrote:
I still wonder though whether a nicer way would be for the configs to be refactored so that -msoft-float was not set on platforms where it wasn't appropriate.
We've gone over this before (so there's discussions in the archive) but in sum, no, we don't want to get into doing floating point.
Hi Tom,
OK, I'll look for those discussions for more background. Just in case there's any misunderstanding, though, I wasn't advocating using floating point, I just meant that U-Boot code might want to perform operations such as long long integer division, which will invoke a libgcc function such as __udivdi3(), and for the linking to succeed we need to ensure that U-Boot and libgcc are using the same ABI. On a fully hard-float system, removing the -msoft-float compilation option seems a good way of achieving that.
Thanks, B.R.