On Wed, Oct 30, 2013 at 9:42 AM, dlewin555 <[email protected]> wrote: > I think that it can be -at worst -ambiguous, not so wrong: let me resay it : > > "Nevertheless,the only reference to the fp operation context switch cost > I've found is related to the VFP which we don't use ONLY with the Sitara > under Angstrom" as we are talking about hardfloat and softfloat , vfpv3 is > not used as is ( read soft/softfp) . when hard for gcc option is used this > implies neon : then your code will be VFP3 and SIMD codes. > Hope this is clearer.
"hard" with gcc doesn't actually imply neon either.. 'armhf' in ubuntu/debian is actually built for "--with-fpu=vfpv3-d16 --with-float=hard --with-mode=thumb" which allows "non-neon" implementations (such as the tegra2 and one marvel chip) to use it. Whereas Angstrom for the beagle has always used the full floating point resources as the omap/sitara parts from TI have the full 32 register vfpv3 with neon implementation.. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
