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. Le mercredi 30 octobre 2013 14:36:21 UTC+1, RobertCNelson a écrit : > > > > > On Wed, Oct 30, 2013 at 3:24 AM, dlewin555 <[email protected]<javascript:> > > wrote: > >> Interesting.Nevertheless,the only reference to the fp operation context >> switch cost I've found is related to the VFP which we don't use with the >> Sitara under Angstrom. >> > > Wow, way wrong... Angstrom has "always" utilized the floating point unit > on these parts. Even way before the "armhf" versions of ubuntu/debian and > fedora came out. The only thing that hasn't changed yet, is to use the > same armhf linker those guys use (/lib/ld-linux-armhf.so.3). > > 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.
