Open escherstair opened 1 month ago
@escherstair You're right. It needs more documentatiom. You only need to keep
ARM_MATH_LOOPUNROLL
DISABLEFLOAT16
Thanks @christophe0606
I'll wait for the documentation.
In the meanwhile, should I change my source code for every compiler define I remove?
Or is arm_rfft_fast_init_4096_f32
the only change needed?
Normally arm_rfft_fast_init_4096_f32
is the only change. Like that the linker js able to infer what you really use and can optimize out the code and tables not needed.
Note that some tables do not actually yield savings right now, even if using the dedicated initialization function. In particular, using the arm_rfft_init_LENGTH_q15
functions will still always take maximum amount of space. Ref issue: https://github.com/ARM-software/CMSIS-DSP/issues/25
I see the new section Code Size in README.md that states:
The general idea is clear, but the steps needed to migrate a legacy project that uses all the old compiler directives is not. As an example, my project uses all the following compiler directives
I cannot use anymore
ARM_DSP_CONFIG_TABLES
and I get the error. I know in advance that I need a real FFT over 4046 samples, and so I have to replace myarm_rfft_fast_init_f32
witharm_rfft_fast_init_4096_f32
(if I'm right). But what about all the other compiler defines? Should I remove all of them (refactoring in some way my source code)?Can you provide a migration guide for this breaking change feature?