search for: ne10_int32

..._float32_neon will scale the output. So we can remove need for one buffer on stack mentioned below. As for the _t API style, it may confuse existing users if we provide two API for the same functionality or if we modify the existing API. How about we keep the typedefs in Opus? For example: typedef ne10_int32_t ne10_int32; typedef ne10_fft_cpx_float32_t ne10_fft_cpx_float32; It would not be too ugly if we put them together somewhere and document them well enough. It is a tiny cost to integrate a 3rd party library. What's more, we have provided a wrapper for NE10_FREE, so that we can make sure memo...

...y want to avoid putting runtime checks if nfft is power of 2 in opus_fft_float_neon. > > As for the _t API style, it may confuse existing users if we provide two API for the same functionality or if we modify the existing API. How about we keep the typedefs in Opus? For example: > typedef ne10_int32_t ne10_int32; > typedef ne10_fft_cpx_float32_t ne10_fft_cpx_float32; > > It would not be too ugly if we put them together somewhere and document them well enough. It is a tiny cost to integrate a 3rd party library. Timothy/All, Can we please get some guidance/consensus on this so we can m...

Viswanath Puttagunta wrote: > Is the peak stack usage a complete blocker in current form? Since this only affects people who enable NE10, I don't think this is a blocker.