search for: config_ti_c54x

Displaying 8 results from an estimated 8 matches for "config_ti_c54x".

2008 Jan 22
2
Shift count warning messages
...he ones that the compiler does not > find. EXTEND32 is usually the cure there also. > > Now that I look at mdf.c, though, W is declares as spx_word32_t, so > there should not be a problem, unless spx_word32_t is being mapped to > 16-bits. That should not happen if you compile with CONFIG_TI_C54X > defined. This is odd. In both cases, what I'm seeing is that the code does a shift right by more than 16 bits. Is it possible that the C5x doesn't want to do that, even for 32-bit operands? It's either that or there's a build problem that causes the operands to be 16 bit inst...
2008 Jan 22
2
Shift count warning messages
yes, our DSP is 16 bit based, and if those bits of code aren't using 32 bit variables then yes that is what the warnings would be. Does this mean that the preprocessor and echo canceller won't work as well because of this? -Mike >>> Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> 01/18/08 8:42 PM >>> I think these warnings are due to your DSP being 16-bit and
2008 Jan 23
2
Shift count warning messages
...>> find. EXTEND32 is usually the cure there also. >>> >>> Now that I look at mdf.c, though, W is declares as spx_word32_t, so >>> there should not be a problem, unless spx_word32_t is being mapped to >>> 16-bits. That should not happen if you compile with CONFIG_TI_C54X >>> defined. This is odd. >> >> In both cases, what I'm seeing is that the code does a shift right by >> more than 16 bits. Is it possible that the C5x doesn't want to do that, >> even for 32-bit operands? It's either that or there's a build problem...
2008 Jan 22
0
Shift count warning messages
...e trickier problems are the ones that the compiler does not find. EXTEND32 is usually the cure there also. Now that I look at mdf.c, though, W is declares as spx_word32_t, so there should not be a problem, unless spx_word32_t is being mapped to 16-bits. That should not happen if you compile with CONFIG_TI_C54X defined. This is odd. - Jim ----- Original Message ----- From: Michael Jacobson To: Jean-Marc Valin Cc: speex-dev@xiph.org Sent: Tuesday, January 22, 2008 9:54 AM Subject: Re: [Speex-dev] Shift count warning messages yes, our DSP is 16 bit based, and if those bits of code ar...
2008 Jan 26
1
Shift count warning messages
...lly the cure there also. >>>>> >>>>> Now that I look at mdf.c, though, W is declares as spx_word32_t, so >>>>> there should not be a problem, unless spx_word32_t is being mapped to >>>>> 16-bits. That should not happen if you compile with CONFIG_TI_C54X >>>>> defined. This is odd. >>>> >>>> In both cases, what I'm seeing is that the code does a shift right by >>>> more than 16 bits. Is it possible that the C5x doesn't want to do that, >>>> even for 32-bit operands? It's ei...
2008 Jan 23
0
Shift count warning messages
...mpiler does not >> find. EXTEND32 is usually the cure there also. >> >> Now that I look at mdf.c, though, W is declares as spx_word32_t, so >> there should not be a problem, unless spx_word32_t is being mapped to >> 16-bits. That should not happen if you compile with CONFIG_TI_C54X >> defined. This is odd. > > In both cases, what I'm seeing is that the code does a shift right by > more than 16 bits. Is it possible that the C5x doesn't want to do that, > even for 32-bit operands? It's either that or there's a build problem > that causes th...
2008 Jan 25
0
Shift count warning messages
...EXTEND32 is usually the cure there also. >>>> >>>> Now that I look at mdf.c, though, W is declares as spx_word32_t, so >>>> there should not be a problem, unless spx_word32_t is being mapped to >>>> 16-bits. That should not happen if you compile with CONFIG_TI_C54X >>>> defined. This is odd. >>> >>> In both cases, what I'm seeing is that the code does a shift right by >>> more than 16 bits. Is it possible that the C5x doesn't want to do that, >>> even for 32-bit operands? It's either that or there...
2015 Jun 03
5
[PATCH 1/1] Updated opus_types.h to correctly support 8 and 64 bit types.
...opus_int8; + typedef unsigned char opus_uint8; typedef signed short opus_int16; typedef unsigned short opus_uint16; typedef signed int opus_int32; typedef unsigned int opus_uint32; + typedef signed long long opus_int64; + typedef unsigned long long opus_uint64; #elif defined(CONFIG_TI_C54X) || defined (CONFIG_TI_C55X) + typedef char opus_int8; + typedef unsigned char opus_uint8; typedef short opus_int16; typedef unsigned short opus_uint16; typedef long opus_int32; typedef unsigned long opus_uint32; + typedef long long opus_int64; + typedef unsigned long long o...