So with this patch, GCC can be configured using any tuple matching arm-*-linux-*eabi* ... but they will all behave in exactly the same way. Is this the intention?
I would have expected that using the eabihf tuple would actually cause GCC to default to hard-float ...
So with this patch, GCC can be configured using any tuple matching arm-*-linux-*eabi* ... but they will all behave in exactly the same way. Is this the intention?
I would have expected that using the eabihf tuple would actually cause GCC to default to hard-float ...