Corrected memory issue in IORunner when using static buffer of
parameters.
Added script to generate a db of regression
Added max regression coef to summary results.
Added some calibration to remove overhead in the benchmark measurement process.
Reorganized one test to move some initialization code outside of the test.
Reorganized code : Testing and benchmarking code in different folders.
Corrected small bug in framework wehn reading parameter files (wrong
number of parameter combinations).
Added benchmarking code for ComplexMathFunctions and some parts of
FilteringFunctions.
(For our internal use. In short term, we won't give support about it).
CMSIS-DSP: Update to cmake build for the testing framework
CMSIS-NN:Implementation of arm_fully_connected_s8
Use API and quantization compatible with TF Lite.
default behavior.
Default behavior is that all tests are enabled by default.
No need to define new compilation flags to enable them.
But there is a new mode which when enabled will allow to select which
tests must be run or not.
By default, this new mode is disabled and in this case all tests will
run.
DSP_Lib_TestSuite can be built with cmake and run on FVP.
Some issues with CMSIS-DSP cmake where discovered and corrected.
Comments added to arm_biqaud_cascade_df2T+f32 since the Neon version
must be initialized differently (and thus the corresponding test
in DSP_Lib_TestSuite will have to be updated to pass with Neon version).
The goal of this commit is to allow the build of CMSIS-DSP on Windows to
enable the use of the library from Python or Matlab.
The Python wrapper has also been simplified and is now using the
CMSIS-DSP directly without requiring specific include files or source files.
Compilation symbols have been introduced to allow to include only the
FFT tables which are useful in a given application.
The README.md in DSP is giving more details.
It is not replacing the current MDK and ArmDS projects.
It is a complementary way to build CMSIS-DSP.
Current version is supporting ARM AC6 compiler from ArmDS.
The result of the build can be run on a FVP for instance.
It could be extended to use different toolchain and build for different
targets.
The README.md in DSP folder is giving all the details.