Hi Richard, I guess we could have builds for AVX and AVX2, or auto detect the level of AVX support and select the appropriate functions at run-time. However the latter would require some more coding work.
Suggest as a first step, we simply build for AVX. It would also be nice to sanity check the availability of AVX at run time, just before any 2020 code runs. Not sure how to do that at run time from C. Cheers, David On 23/04/19 23:46, Richard Shaw wrote: > Ok, sorry for the multiple emails but as I think about it I keep coming > up with more questions. :) > > Are we taking advantage of the capabilities that AVX2 provide? Or should > we just standardize on AVX? > > Could we assume AVX on i686 and AVX2 on x86_64 systems? > > AVX gets us processors in the 2011 era and AVX2 2013 (intel) 2015 (AMD) > but it appears to only be definitely available in Core processors on > Intel, not necessarily Pentium or Celeron. > > Thanks, > Richard > > > > > _______________________________________________ > Freetel-codec2 mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 > _______________________________________________ Freetel-codec2 mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freetel-codec2
