search for: gnulinux_config

Viswanath Puttagunta wrote: > Can we please have review on RFCv2? We have quite a few optimizations > (Eg: ifft/mdct_backwards, fixed point fft/ifft mdct_forward/backward > etc) that are in my pipeline that depend on this patch series being > accepted. So, trying to make progress on this... On an armv7l board running Ubuntu, you've broken the build with just --enable-intrinsics

...are also > incorrect. I don't know if -DGNULINUX_PLATFORM=ON does anything, but I > needed to specify -DNE10_LINUX_TARGET_ARCH=armv7 to avoid cmake failing with > a 'syntax error' at line 83. I use the following commands cmake -DNE10_BUILD_SHARED=ON -DCMAKE_TOOLCHAIN_FILE=../ GNUlinux_config.cmake .. The GNUlinux_config.cmake sets up any other variables. I will update this in libNE10. > > > In short, this needs some work. Yep, Will get back to you by end of this week at the latest.

...can see my working NE10 code at https://git.linaro.org/people/viswanath.puttagunta/Ne10.git (branch: rfcv2_ne10_fft) My compile instructions: git clone https://github.com/projectNe10/Ne10.git cd Ne10 && mkdir build && cd build cmake -DNE10_BUILD_SHARED=ON -DCMAKE_TOOLCHAIN_FILE=../GNUlinux_config.cmake .. make -j6 Timothy/All. Having scaling capability for non-power-of-2 will work for non-custom modes(nfft = 60, 120, 240 and 480). What should we do for power-of-2? I really want to avoid putting runtime checks if nfft is power of 2 in opus_fft_float_neon. > > As for the _t API style...

Hi all, I have already added support for scaled forward non-power-of-2 floating-point FFT: https://github.com/projectNe10/Ne10/commit/79c3d787302f8d74b9bcfe6545d487cdf1b101d9 Two flags are added to cfg structure: is_forward_scaled and is_backward_scaled. By setting is_forward_scaled to anything but zero, ne10_fft_c2c_1d_float32_neon will scale the output. So we can remove need for one buffer on