search for: override_speex_warning

...either through conditional compilation or may be even with configuration perl script) would be simple than specific DISABLE_VOCODER. Another potential saving could be achieved by replacing speex_warning, speex_notification and speex_error with user-modifiable defines. The existing DISABLE_WARNING/ OVERRIDE_SPEEX_WARNING method is not efficient in reducing the code footprint because the majority of the overhead happens in the points of invocation of the speex_warning rather than in the function itself. With all my suggestion applied there is an opportunity that minimized speex would fit in on-chip code memory of B...

...e of internal functioning of the library. I think, DISABLE_VBR is a good candidate for official release. >> Another potential saving could be achieved by replacing speex_warning, speex_notification >> and speex_error with user-modifiable defines. The existing DISABLE_WARNING/ >> OVERRIDE_SPEEX_WARNING method is not efficient in reducing the code footprint because the >> majority of the overhead happens in the points of invocation of the speex_warning rather than >> in the function itself. > >How about: >#define OVERRIDE_SPEEX_WARNING >#define speex_warning(x) {} >in us...