Displaying 3 results from an estimated 3 matches for "nb_encoder_int".
Did you mean:
nb_encoder_init
2005 May 24
2
Speex on TI C6x, Problem with TI C5x Patch
Skipped content of type multipart/alternative-------------- next part --------------
A non-text attachment was scrubbed...
Name: maleout12may.wav
Type: audio/wav
Size: 95884 bytes
Desc: not available
Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20050524/57112d0c/maleout12may-0001.bin
2005 May 24
0
Speex on TI C6x, Problem with TI C5x Patch
...nfigure tools, so I needed to create
> speex_config_types.h (short and int are 16, long is 32 on C5x).
That, or you could add an entry in the speex_types.h file (which is used
for all platforms that don't use autoconf).
> 3. And, of course, the internal stack memory allocations in
> nb_encoder_int and nb_decoder_init had to be cut down to fit within
> the available data memory space. It would be useful to parameterize
> the working stack allocation size for those folks who cannot use the
> new VAR_ARRAYS and USE_ALLOCA stuff.
Would a compile-time option be OK (so I don't need...
2005 May 25
3
Speex on TI C6x, Problem with TI C5x Patch
...or would work too.
> Eventually, this could probably made to fit in a 32-bit int, but I
> haven't done that yet.
The C55x uses a 40-bit long long (as Stuart Cording pointed out), so this
should be fine here.
>> 3. And, of course, the internal stack memory allocations in
>> nb_encoder_int and nb_decoder_init had to be cut down to fit within
>> the available data memory space. It would be useful to parameterize
>> the working stack allocation size for those folks who cannot use the
>> new VAR_ARRAYS and USE_ALLOCA stuff.
>
> Would a compile-time option be OK...