Displaying 3 results from an estimated 3 matches for "ne10_fft_state_float32".
Did you mean:
ne10_fft_state_float32_
2015 Feb 03
2
opus Digest, Vol 72, Issue 17
...h Phil at NE10_ARM. He committed
> to two changes:
> 1. Change API to address usage of _t from NE10 api for following types:
> ne10_int32_t ------> will become ----> ne10_int32
> ne10_fft_cpx_float32_t ------> will become ----> ne10_fft_cpx_float32
> ne10_fft_state_float32_t ------> will become ---> ne10_fft_state_float32
> ne10_fft_cfg_float32_t -----> will become ----> ne10_fft_cfg_float32
>
> 2. Provide scaling as argument to ne10_fft_c2c_1d_float32_neon() and
> remove need for one buffer on stack (ALLOC(tempin, st->nfft,
> ne10_...
2015 Jan 30
1
[RFC PATCH v1 2/2] armv7(float): Optimize encode usecase using NE10 library
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.
2015 Feb 04
0
opus Digest, Vol 72, Issue 17
...He committed
>> to two changes:
>> 1. Change API to address usage of _t from NE10 api for following types:
>> ne10_int32_t ------> will become ----> ne10_int32
>> ne10_fft_cpx_float32_t ------> will become ----> ne10_fft_cpx_float32
>> ne10_fft_state_float32_t ------> will become ---> ne10_fft_state_float32
>> ne10_fft_cfg_float32_t -----> will become ----> ne10_fft_cfg_float32
>>
>> 2. Provide scaling as argument to ne10_fft_c2c_1d_float32_neon() and
>> remove need for one buffer on stack (ALLOC(tempin, st->...